Re: Bug in Dependencies Code in 7.3.x?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tara Piorkowski <tara(at)vilaj(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bug in Dependencies Code in 7.3.x?
Date: 2002-12-31 17:41:51
Message-ID: 1192.1041356511@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>>> Seems this is already a TODO:
>>> * Have sequence dependency track use of DEFAULT sequences, seqname.nextval
>>
>> That's related but not the same issue.

> Related in that ALTER TABLE DROP DEFAULT _doesn't_ see a dependancy for
> sequences in a DEFAULT?

Even if the dependency generator understood about nextval, it would
generate a dependency from the expression to the sequence, not vice
versa --- ie, the system would prevent you from dropping the sequence
without dropping the default expression. It would not prevent ALTER
TABLE DROP DEFAULT, which is what's at issue here.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-12-31 17:49:29 Re: PostgreSQL Password Cracker
Previous Message Tom Lane 2002-12-31 17:38:29 Re: PostgreSQL Password Cracker