| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |
| Date: | 2014-01-18 13:28:14 |
| Message-ID: | CA+TgmoadQnPMVPDsSuZhmh96GwJ5YGgrKxNhbGe9RUSRK4VxSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 16, 2014 at 3:35 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> Makes sense. Can you extract that into a separate patch, please?
>
> I was wondering if that might cause deadlocks if an existing index is
> changed from unique to non-unique, or vice versa, as the ordering would
> change. But we don't have a DDL command to change that, so the question is
> moot.
It's not hard to imagine someone wanting to add such a DDL command.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-01-18 13:31:55 | Re: Changeset Extraction v7.0 (was logical changeset generation) |
| Previous Message | Robert Haas | 2014-01-18 13:25:48 | Re: ALTER TABLESPACE ... MOVE ALL TO ... |