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

Re: pg_dump: use ALTER TABLE for PKs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump: use ALTER TABLE for PKs
Date: 2002-02-19 15:09:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> I can't really think of a case where the index OID would be less than the
> table OID, but it might be good to put the table OID in the deps list; this
> will force the PK to go after the table in all cases. Did I mention I'm
> paranoid?

After OID-counter wraparound it'd be quite easy to have such a case.

To the extent that pg_dump is depending on OID comparison to tell it
something about creation order, it's really broken and should be fixed.
The dependencies mechanism should eventually be extended to cover all
these relationships.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Salil MohantyDate: 2002-02-19 15:13:00
Subject: a question on backup
Previous:From: Tom LaneDate: 2002-02-19 14:54:57
Subject: Re: Transient Disk Usage Higher In 7.2 ?

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