]> granicus.if.org Git - postgresql/commit
Don't needlessly check the partition contraint twice
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 11 Jun 2018 20:53:33 +0000 (16:53 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 11 Jun 2018 21:12:16 +0000 (17:12 -0400)
commit5b0c7e2f757a2cbdd8e0c478de51bcb5606d3a93
tree2980f038b577b75368a597d66a055d90604990ee
parent85dd744a70d167ca86e83ea38f5ac3e1449bb028
Don't needlessly check the partition contraint twice

Starting with commit f0e44751d717, ExecConstraints was in charge of
running the partition constraint; commit 19c47e7c8202 modified that so
that caller could request to skip that checking depending on some
conditions, but that commit and 15ce775faa42 together introduced a small
bug there which caused ExecInsert to request skipping the constraint
check but have this not be honored -- in effect doing the check twice.
This could have been fixed in a very small patch, but on further
analysis of the involved function and its callsites, it turns out to be
simpler to give the responsibility of checking the partition constraint
fully to the caller, and return ExecConstraints to its original
(pre-partitioning) shape where it only checked tuple descriptor-related
constraints.  Each caller must do partition constraint checking on its
own schedule, which is more convenient after commit 2f178441044 anyway.

Reported-by: David Rowley
Author: David Rowley, Álvaro Herrera
Reviewed-by: Amit Langote, Amit Khandekar, Simon Riggs
Discussion: https://postgr.es/m/CAKJS1f8w8+awsxgea8wt7_UX8qzOQ=Tm1LD+U1fHqBAkXxkW2w@mail.gmail.com
src/backend/commands/copy.c
src/backend/executor/execMain.c
src/backend/executor/execPartition.c
src/backend/executor/execReplication.c
src/backend/executor/nodeModifyTable.c
src/include/executor/executor.h