Re: Non-colliding auto generated names - Mailing list pgsql-patches

From Tom Lane
Subject Re: Non-colliding auto generated names
Date
Msg-id 23284.1045579418@sss.pgh.pa.us
Whole thread Raw
In response to Re: Non-colliding auto generated names  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: Non-colliding auto generated names  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-patches
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> And if your 'name prediction' code can't deal with collisions, then
> it needs help.

THe point is that right now, if you know the CREATE TABLE command, then
you can compute exactly what index names it will assign --- no outside
knowledge about the previous state of the database is required.

I'm not sure how significant that really is to anyone, but it is
something that we'd be giving up.

And as I said, I don't have a better answer.  I'm just expressing
vague unease, in hopes that it might spur someone to think of another
way.  I'm willing to go with this way if we don't find another.

            regards, tom lane

pgsql-patches by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: pg_avd
Next
From: greg@turnstep.com
Date:
Subject: Re: FAQ addition: deleteing all but one unique row