Thats fair, and makes the job a heck of a lot simpler. We do need to change the sequence naming once. They have a tendency to conflict at the moment.
-- Rod ----- Original Message ----- From: "Tom Lane" <[EMAIL PROTECTED]> To: "Rod Taylor" <[EMAIL PROTECTED]> Cc: "Hackers List" <[EMAIL PROTECTED]> Sent: Thursday, June 13, 2002 6:05 PM Subject: Re: [HACKERS] Making serial survive pg_dump > "Rod Taylor" <[EMAIL PROTECTED]> writes: > > If we have sequences pick new names automatically, it may not pick the > > same name after dump / restore as it had earlier -- especially across > > versions (see TODO entry). > > So don't we need a way to suggest the *right* name to SERIAL? > > No. IMHO, if we change the naming convention for serial sequences (which > seems unlikely, except that it might be indirectly affected by changing > NAMEDATALEN), then we'd *want* the new naming convention to take effect, > not to have pg_dump scripts force an old naming convention to be > preserved. > > I realize there's a potential for failing to restore the setval() > information if the name actually does change, but I'm willing to live > with that. > > regards, tom lane > ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
