pgsql: Don't invoke arbitrary code inside a possibly-aborted transactio

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't invoke arbitrary code inside a possibly-aborted transactio
Date: 2017-01-24 14:01:18
Message-ID: E1cW1ew-0007wn-41@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Don't invoke arbitrary code inside a possibly-aborted transaction.

The code here previously tried to call the partitioning operator, but
really the right thing to do (and the safe thing to do) is use
datumIsEqual().

Amit Langote, but I expanded the comment and fixed a compiler warning.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/289992c462b504ffa289202ce8fc34a56b4048c3

Modified Files
--------------
src/backend/catalog/partition.c | 20 ++++++++++++++------
src/backend/utils/adt/datum.c | 4 ++++
2 files changed, 18 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2017-01-24 14:08:39 pgsql: Remove unused variable.
Previous Message Robert Haas 2017-01-24 13:50:34 pgsql: Fix interaction of partitioned tables with BulkInsertState.