Re: adsrc and consrc incompatible with rename operations

From: Rod Taylor <rbt(at)rbt(dot)ca>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: adsrc and consrc incompatible with rename operations
Date: 2003-06-27 13:27:37
Message-ID: 1056720457.25229.4.camel@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2003-06-27 at 08:36, Peter Eisentraut wrote:
> The system catalog columns pg_attrdef.adsrc and pg_constraint.consrc store
> "human-readable" versions of pg_attrdef.adbin and pg_constraint.conbin.
> During a rename operation, they are not and cannot be updated. We need to
> remove them and make interested applications get the information about of
> the *bin columns. I noticed that various functions were recently updated
> to do that, but I think the columns should be removed altogether because
> they cannot be trusted.

Agreed (even brought it up at the time), but there are some
circumstances that may cause the binary column to be irretrievable due
to a corrupt system catalogue -- which is still possible despite
dependencies (concurrency issues -- lack of object locking).

--
Rod Taylor <rbt(at)rbt(dot)ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Srikanth M 2003-06-27 13:44:33 CODE SUBMISSION FOR NEXT RELEASE
Previous Message John DeSoi 2003-06-27 12:48:14 Re: row description for domain in 7.4