| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Subject: | Re: UPSERT wiki page, and SQL MERGE syntax |
| Date: | 2014-10-03 22:49:15 |
| Message-ID: | CAM3SWZQB8AKj6WKu7ErUk67a2EW7gwoy7tJmotYX7ugqFjSEQQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 3, 2014 at 3:42 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> We routinely pick very
>> different plans based on the presence or absence of an index, and
>> we use special snapshots in the course of executing many DML
>> statements (if FK triggers are fired)
Apart from FK snapshots, we also use dirty snapshots for unique index
enforcement, obviously. That doesn't mean that it's the "command/xact
snapshot", though. It's just a special constraint enforcement
mechanism.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2014-10-03 23:00:36 | Re: Fixed xloginsert_locks for 9.4 |
| Previous Message | Peter Geoghegan | 2014-10-03 22:43:18 | Re: UPSERT wiki page, and SQL MERGE syntax |