From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Brent Verner <brent(at)rcfile(dot)org> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Quick question |
Date: | 2001-11-13 18:37:59 |
Message-ID: | 3003.1005676679@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Brent Verner <brent(at)rcfile(dot)org> writes:
> ISTM, that these sequences created by way of a SERIAL type should
> be named "pg_serial_test_id_HASH" or similar, since they are system
> (bookkeeping) rels. Also, I /personally/ would like it if the sequence
> was dropped along with the table using it, provided that no other atts
> in the system are using it.
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.
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2001-11-13 18:48:12 | aggregate functions for inet ? |
Previous Message | Bruce Momjian | 2001-11-13 18:36:12 | Re: Open items |