Skip site navigation (1) Skip section navigation (2)

Re: Arrays vs separate system catalogs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Arrays vs separate system catalogs
Date: 2002-02-27 22:03:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> 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?

Seems like an array is a perfectly fine representation, and what's
lacking are suitable operators.  Maybe we should think about inventing
some operators, rather than giving up on arrays.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Neil ConwayDate: 2002-02-27 22:34:58
Subject: Re: eWeek Poll: Which database is most critical to your
Previous:From: mlwDate: 2002-02-27 21:44:21
Subject: Re: Oracle vs PostgreSQL in real life

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group