mirror of https://github.com/postgres/postgres
Starting with commitpull/32/headf0e44751d7
, ExecConstraints was in charge of running the partition constraint; commit19c47e7c82
modified that so that caller could request to skip that checking depending on some conditions, but that commit and15ce775faa
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 commit2f17844104
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
parent
85dd744a70
commit
5b0c7e2f75
Loading…
Reference in new issue