From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Possible patch for better index name choosing |
Date: | 2009-12-21 05:39:16 |
Message-ID: | 27774.1261373956@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Perhaps I should RTFP before sticking my neck out too far,
> but... will you serialize EXCLUDE (a =), EXCLUDE (a &&), and EXCLUDE
> (a <some other operator>) differently?
No, and I'm not proposing to expose ASC/DESC/NULLS FIRST/LAST or
nondefault opclasses (to say nothing of non-btree AMs) or index
predicates either. The proposed patch is to my mind just a logical
extension of what we have always done --- namely, to pay attention
to index column names --- to some new cases that were never exposed
before.
We could certainly make it pay attention to all that stuff, but I have
the same feeling you do that it wouldn't produce readable results.
And it would make any compatibility issues a lot worse.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-12-21 05:48:15 | Re: Proposal: Pre ordered aggregates, default ORDER BY clause for aggregates - median support |
Previous Message | Bruce Momjian | 2009-12-21 05:29:48 | Re: Removing pg_migrator limitations |