| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Patches" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Non-colliding auto generated names |
| Date: | 2003-02-18 06:10:01 |
| Message-ID: | 073e01c2d714$5efc3560$6500a8c0@fhp.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I thought folks wanted them to fail if they conflicted so that they
> > could know for sure how to derive such names definitively. Is that
> > accurate?
>
> It sort of bothers me that this patch would make it impossible to
> predict with certainty the index names associated with a table.
> But I haven't got a better idea...
OK, but why would you need to be able to do that? Also, it tells you in the
notice. And if your 'name prediction' code can't deal with collisions, then
it needs help. Also, what's stopping you specifying the name explicitly?
Maybe we could put it to pgsql-general?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Curt Sampson | 2003-02-18 06:14:08 | Re: Detecting corrupted pages earlier |
| Previous Message | Tom Lane | 2003-02-18 06:00:12 | Re: Non-colliding auto generated names |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2003-02-18 08:08:11 | fix tiny psql memory leak |
| Previous Message | Tom Lane | 2003-02-18 06:00:12 | Re: Non-colliding auto generated names |