Re: Bug in Dependencies Code in 7.3.x?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(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 18:04:43
Message-ID: 200212311804.gBVI4h324893@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


I get it, mutual dependency because they are both droppable. Added to
TODO:

* Have DEFAULT dependency track use of sequence, for DROP DEFAULT check

---------------------------------------------------------------------------

Tom Lane wrote:
> 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
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Elphick 2002-12-31 19:17:46 Re: PostgreSQL Password Cracker
Previous Message Tom Lane 2002-12-31 18:04:13 Re: PostgreSQL Password Cracker