From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mike Sosteric <mikes(at)athabascau(dot)ca> |
Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-general(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [SQL] arrays |
Date: | 2002-09-30 14:42:08 |
Message-ID: | 21137.1033396928@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-sql |
Mike Sosteric <mikes(at)athabascau(dot)ca> writes:
> could you select where title[0] = 'en'
You certainly could ... but bear in mind that there's no convenient way
to make such a query be indexed, at present. So any values that you
actually want to use as search keys had better be in their own fields.
Now, if you are just using this as an extra search condition that picks
one row out of a small number that are identified by another WHERE
clause, then it's good enough to index for the other clause, and so the
lack of an index for title[0] isn't an issue. In this case, with only
a small number of possible values for title[0], it seems that an index
wouldn't be helpful anyway.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-30 14:57:00 | Re: Beta2 - A Late Announcement |
Previous Message | Adam Witney | 2002-09-30 14:41:09 | Re: Beta2 - A Late Announcement |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-09-30 14:48:43 | Re: Do we want a CVS branch now? |
Previous Message | Justin Clift | 2002-09-30 14:37:13 | Re: Cause of missing pg_clog files |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2002-09-30 15:54:31 | Re: [GENERAL] arrays |
Previous Message | Bruno Wolff III | 2002-09-30 13:57:33 | Re: [SQL] arrays |