From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Brent Verner <brent(at)rcfile(dot)org>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Quick question |
Date: | 2001-11-22 01:34:11 |
Message-ID: | 200111220134.fAM1YBK29410@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > I think there are two completely different issues here: one is what
> > name to use for the auto-generated sequence, and the other is whether
> > (when) to drop the sequence if the table is dropped. Fixing the
> > latter issue would reduce but not entirely eliminate the issue of
> > name collisions.
>
> Hmmm? No way - see below.
>
> > IIRC, the major objection to the notion of adding random hash characters
> > to the auto-generated names was that people wanted to be able to predict
> > the names. There was a long discussion about this a couple years back
> > when we settled on the present algorithm. Please search the archives
> > a bit if you want to re-open that issue.
>
> I will search the archives, but I'll explain my thoughts here a well.
>
> Well, what's the problem with appending a number - that's how index names
> get generated.
>
> This is my horrible schema that forced me to abandon using SERIAL in favour
> of explicit CREATE SEQUENCE statements:
Added to TODO:
* Have SERIAL generate non-colliding sequence names when we have
auto-destruction
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-11-22 01:40:46 | Re: TOAST performance (was Re: [GENERAL] Delete Performance) |
Previous Message | Serguei Mokhov | 2001-11-22 01:23:24 | Mention NLS option in INSTALL |