pgsql: Fix ON CONFLICT DO UPDATE for tables with oids.

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix ON CONFLICT DO UPDATE for tables with oids.
Date: 2015-09-28 17:31:27
Message-ID: E1ZgcGt-0001Te-BK@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix ON CONFLICT DO UPDATE for tables with oids.

When taking the UPDATE path in an INSERT .. ON CONFLICT .. UPDATE tables
with oids were not supported. The tuple generated by the update target
list was projected without space for an oid - a simple oversight.

Reported-By: Peter Geoghegan
Author: Andres Freund
Backpatch: 9.5, where ON CONFLICT was introduced

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/617db3a2d8ad6abc0d7be623f43edc943a6640a8

Modified Files
--------------
src/backend/executor/nodeModifyTable.c | 2 +-
src/test/regress/expected/insert_conflict.out | 59 +++++++++++++++++++++++++
src/test/regress/sql/insert_conflict.sql | 22 +++++++++
3 files changed, 82 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2015-09-28 17:31:29 pgsql: Fix ON CONFLICT DO UPDATE for tables with oids.
Previous Message Robert Haas 2015-09-28 15:01:33 pgsql: Use LOCKBIT_ON() instead of a bit shift in a few places.