| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Minor ON CONFLICT related fixes |
| Date: | 2015-05-18 20:53:39 |
| Message-ID: | CAM3SWZT1qX+jWg6UUP3-Gp3EuztoFYWchsM2TkJP_WWHoXGFaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 18, 2015 at 1:49 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> Here is a cumulative version of what was previously posted.
BTW, this could result in more calls to get_opclass_family() and
get_opclass_input_type() than before. However, because we'll have
eliminated so many candidates (e.g. by seeing that they're not unique
indexes) by the time the call to infer_collation_opclass_match() comes
anyway, and because it's so rare to have to specify an opclass at all,
I thought this was fine.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2015-05-18 20:54:33 | Re: jsonb concatenate operator's semantics seem questionable |
| Previous Message | Alvaro Herrera | 2015-05-18 20:52:22 | Re: 9.5 open items |