| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Rod Taylor" <rbt(at)zort(dot)ca> |
| Cc: | "Hackers List" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Making serial survive pg_dump |
| Date: | 2002-06-13 22:05:12 |
| Message-ID: | 297.1024005912@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Rod Taylor" <rbt(at)zort(dot)ca> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-06-13 22:11:05 | Re: Making serial survive pg_dump |
| Previous Message | Rod Taylor | 2002-06-13 21:56:42 | Re: Making serial survive pg_dump |