Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE - Mailing list pgsql-hackers

From Robert Haas
Subject Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Date
Msg-id CA+TgmoadQnPMVPDsSuZhmh96GwJ5YGgrKxNhbGe9RUSRK4VxSQ@mail.gmail.com
Whole thread Raw
In response to Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Thu, Jan 16, 2014 at 3:35 AM, Heikki Linnakangas
<hlinnakangas@vmware.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: ALTER TABLESPACE ... MOVE ALL TO ...
Next
From: Robert Haas
Date:
Subject: Re: Changeset Extraction v7.0 (was logical changeset generation)