| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Possible patch for better index name choosing |
| Date: | 2009-12-21 22:37:25 |
| Message-ID: | 21780.1261435045@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On mn, 2009-12-21 at 00:03 -0500, Tom Lane wrote:
>> Well, we could tamp down the risks considerably if we undid my point
>> (1), namely to still consider only the first index column when
>> generating a name.
> I think putting all the column names into the index names instead of
> only the first is a significant improvement that should be kept.
Yeah, I think so too. It's well worth any risk of application
incompatibility --- we make much bigger changes in every major
release without blinking.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2009-12-21 22:49:59 | Re: Segfault from PL/Perl Returning vstring |
| Previous Message | David E. Wheeler | 2009-12-21 22:34:17 | Re: Segfault from PL/Perl Returning vstring |