Search Postgresql Archives

Re: Very long "or" where clause

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Richard Huxton <dev@xxxxxxxxxxxx>
Subject: Re: Very long "or" where clause
From: Scara Maccai <m_lists@xxxxxxxx>
Date: Tue, 16 Jan 2007 10:50:09 +0100
Cc: pgsql-general@xxxxxxxxxxxxxx
In-reply-to: <45AC9A4E.2000507@xxxxxxxxxxxx>
References: <45AC9613.6030204@xxxxxxxx> <45AC9A4E.2000507@xxxxxxxxxxxx>
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

Put the test-values into a temporary table, analyse it and then joinagainst it.


Ok, I didn't think of it.

Can't say about indexes without knowing more about yourusage pattern.



What do you mean?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Very long "or" where clause
  - From: Richard Huxton

References:
- Very long "or" where clause
  - From: Scara Maccai
- Re: Very long "or" where clause
  - From: Richard Huxton

Prev by Date: Re: Very long "or" where clause
Next by Date: Re: Very long "or" where clause
Previous by thread: Re: Very long "or" where clause
Next by thread: Re: Very long "or" where clause
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux