On 24 May 2004, at 14:37, Tom Lane wrote:
Dan Field <[EMAIL PROTECTED]> writes:
I have a similar problem with just one of my queries (although it
isn't
a sub select):
You really ought to vacuum and/or analyze occasionally. The EXPLAIN
results show that the planner hasn't got
TRUE) AND (dewey_point_ones IS NULL) AND (dewey_point_tens IS NULL) AND (dewey_point_hundreds IS NULL) AND (dewey_point_thousands IS NULL) AND (dewey_point_tenthousands IS NULL) AND (dewey_point_hundredthousands IS NULL))
(10 rows)
--
Dan Field <[EMAIL PROTECTED]> - Support Programmer: Cymru ar y we
cy_GB: http://www.cymruarywe.org
en_GB: http://www.walesontheweb.org
On 18 May 2004, at 17:12, Bruno Wolff III wrote:
On Tue, May 18, 2004 at 16:47:11 +0100,
Dan Field <[EMAIL PROTECTED]> wrote:
FROM
da_records
WHERE
da_records.DESCRIPTION_CY ~* '.*Aberystwyth*.'
OR
da_records.TITLE_CY ~* '.*Aberystwyth*.'
limit
RIPTION_CY ~* '.*Aberystwyth*.'
OR
da_records.TITLE_CY ~* '.*Aberystwyth*.'
limit 100
Is there a better way of matching the string? (Must be case insensitive)
TIA
--
Dan Field <[EMAIL PROTECTED]> - Support Programmer: Cymru ar y we
cy_GB: http://www.cymruarywe.org
en_GB: http://www.walesontheweb.org
er 10MB total size, so even a complete resultset shouldn't be too much for the machine.
Incidentally the hardware I'm running on is: Dual 2GHz Opteron, 2GB RAM, SCSI. Hardly a slow system!
Any pointers at either, more efficiend SQL or ways to tweak Postgres will be gladly recieved.
Many
r types 'character' and
'boolean' You will have to retype this query using an explicit cast.
Any help would be much appreciated
TIA
--
Dan Field
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
