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

Re: Proposal: move column defaults into pg_attribute along with attacl

From: Markus Wanner <markus(at)bluegap(dot)ch>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org, Stephen Frost <sfrost(at)snowman(dot)net>
Subject: Re: Proposal: move column defaults into pg_attribute along with attacl
Date: 2008-09-23 13:18:39
Message-ID: 48D8ECAF.20705@bluegap.ch (view raw or flat)
Thread:
Lists: pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Tom Lane wrote:
> Well, as far as the dependency system goes this way is more convenient.
> If pg_attribute entries had their own OIDs it would be fairly hard
> to implement DROP TABLE except with an intermediate step of dropping
> each of the columns one by one, because you'd pretty much have to have
> explicit pg_depend entries linking each column to its table, and that
> behavior is what you'd get from the dependency traversal.

So, we do not want attributes to be dependent on the relation, because
that complicates DROP TABLE. On the other hand, we want defaults (and
possibly ACLs) to be dependent, so that the dependency system cleans
them up when dropping the table. It that correct?

ISTM that we should at least combine defaults and ACLs then, as proposed
by Stephen.

Regards

Markus Wanner

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEUEARECAAYFAkjY7K8ACgkQsPwMloDjyo/UGACeI2YA2bAV+NAt3NXNCP641NXP
phAAmPuQRUxkNRQOsVwQAKLNlayuPg4=
=dwXa
-----END PGP SIGNATURE-----

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2008-09-23 13:26:11
Subject: Re: Planner question
Previous:From: Gregory StarkDate: 2008-09-23 13:16:02
Subject: Re: Common Table Expressions (WITH RECURSIVE) patch

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