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: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Rod Taylor <rbt(at)zort(dot)ca>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Open 7.3 issues |
Date: | 2002-08-15 16:30:42 |
Message-ID: | 200208151630.g7FGUg901492@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > coming from 7.2 is going to cause problems in 7.3, i.e. do we make
> > assumptions that dependency info is there and in cases it isn't, are
> > there surprises for users, where things worked fine in 7.2. I want to
> > know if there are cases where we assumed dependency info was there when
> > in 7.2 we handled the lack of depenency better.
>
> No, we have not broken any cases that used to work, AFAIK.
>
> There are new features in 7.3 that will not work in a database made from
> a 7.2 dump --- for example, dropping an old table containing a serial
> column won't make the sequence go away, because we won't have a
> dependency link between the table and the sequence. But it didn't go
> away in 7.2 either, so the behavior's no worse. Another thing we won't
> understand is that certain sets of triggers make up a foreign-key
> constraint, so you won't be able to use ALTER TABLE DROP CONSTRAINT to
> delete 'em. But you couldn't in 7.2 either.
>
> While I've toyed with the notion of trying to intuit these dependencies
> as we reload a database, I'm not at all sure it's a good idea. The
> former 7.2 user might be quite unhappy if we drop a sequence he wasn't
> expecting to have dropped. We cannot tell for certain how the sequence
> was made --- it might have been handmade and then used in an explicit
> DEFAULT expression, in which case an auto-drop dependency would probably
> not be a friendly thing to spring on the user.
>
> The bulk of the new dependencies are made automatically as we handle
> CREATE statements, so they'll be correct in a reloaded database anyway.
> AFAIR it's just serial sequences and foreign keys that are not going to
> be as bright as they might be.
OK, that's what I needed to know. It may be confusing to some users
that 7.2 serial/foreign keys don't auto-drop while 7.3 do. We need to
mention that in the release notes. I think that will be enough, but I
can imagine people dumping/reloading their db's to get that dependency,
and I am not sure how we would tell them to do that.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Vince Vielhaber | 2002-08-15 16:34:40 | Re: Open 7.3 items |
Previous Message | Tom Lane | 2002-08-15 16:20:37 | Re: Open 7.3 issues |