From: | Teodor Sigaev <teodor(at)stack(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Arrays vs separate system catalogs |
Date: | 2002-02-27 21:41:20 |
Message-ID: | 3C7D5280.9080101@stack.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello.
It's more common problem, I think. Working with array in postgres is
very difficult and uncomfortable. For any array type it needs methods
like a push, pop, length, splice etc. This methods may be implemented
for any array type. BTW, aggregates MAX and MIN works only for built-in
types, but such aggregates may be defined for any type which supports
compare function.
Peter Eisentraut wrote:
> During my coding of the per-user/database settings, it occurred to me one
> more time that arrays are evil. Basically, the initial idea was to have a
> column pg_database.datconfig that contains, say,
> '{"geqo_threshold=55","enable_seqscan=off"}'. Just inserting and deleting
> in arrays is terrible, let alone querying them in a reasonable manner.
> We're getting killed by this every day in the privileges and groups case.
>
> What are people's thoughts on where (variable-length) arrays are OK in
> system catalogs, and where a new system catalog should be created?
>
>
--
Teodor Sigaev
teodor(at)stack(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | mlw | 2002-02-27 21:44:21 | Re: Oracle vs PostgreSQL in real life |
Previous Message | Dann Corbit | 2002-02-27 21:33:40 | Re: eWeek Poll: Which database is most critical to |