| From: | Rod Taylor <rbt(at)zort(dot)ca> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: I am done |
| Date: | 2002-09-02 16:45:26 |
| Message-ID: | 1030985127.8617.121.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > * Have SERIAL generate non-colliding sequence names when we have
> > auto-destruction
> >
> > They should be pretty well non-colliding now. What's the gripe exactly?
>
> The issue was that when there were name collisions, we threw an error
> instead of trying other sequence names. We had to do that because we
> needed the sequence name to be predictable so it could be auto-deleted.
> Now with dependency, we don't need to have it be predictable. However,
> we still use nextval() on the sequence name, so we can't say it is
> arbitrary either. Should we just remove the item?
The names are relied on by pg_dump for setting the next value of the
sequence. That is, it relies on the names being generated the exact
same way every time.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-02 16:46:10 | Re: I am done |
| Previous Message | Tom Lane | 2002-09-02 16:39:36 | Re: I am done |