Tom Lane wrote:
> Yah. However, I started to look at doing this and immediately hit a
> stumbling block: we need a representation in pg_depend for a column's
> default expression (as distinct from the column itself).
Just to understand the issue here: what's the reason for having an OID
for the default value and possible another one for a ACLs, but none for
the attribute itself?
Why don't we just have a unique OID for pg_attribute (i.e. drop the
BKI_WITHOUT_OIDS of pg_attribute) and merge in the default values and ACLs?
In response to
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2008-09-23 09:20:40|
|Subject: pgsql: Make LC_COLLATE and LC_CTYPE database-level settings.|
|Previous:||From: Dave Page||Date: 2008-09-23 08:12:16|
|Subject: Re: macport for libpqxx|