| From: | "Steve Howe" <howe(at)carcass(dot)dhs(dot)org> |
|---|---|
| To: | "Joel Burton" <joel(at)joelburton(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Catalogs design question |
| Date: | 2001-10-20 07:55:45 |
| Message-ID: | 001701c1593c$a039b1d0$8430b0c8@angla |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I also quote the PotgreSQL user manual
> >
(http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/arrays.html):
>
> In the contrib/ directory are procedures to search arrays for values.
> This may help.
Thanks for the tip, but in fact I've seen them (and they're listed on the
same document I pointed on the original message).
These are sequential (slow) searches, and can't be indexed. in resume:
nothing but another crude hack :). I could even use it, but I can';t tell my
users "oh this feature works but you must compile this contrib code inyo
your servers". Many users can't do it, and many don't even know how to do it
:(
Best Regards,
Steve Howe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Howe | 2001-10-20 08:06:59 | Re: Catalogs design question |
| Previous Message | Flancer | 2001-10-20 07:27:02 | Re: To Postgres Devs : Wouldn't changing the select limit |