postgresql.git/src/backend/commands/copyfrom.c, branch REL_19_STABLE

Revert UPDATE/DELETE FOR PORTION OF

2026-09-15T10:16:42Z

List of commits reverted: 8e72d914c52 Add UPDATE/DELETE FOR PORTION OF b6ccd30d8ff Add isolation tests for UPDATE/DELETE FOR PORTION OF 33db6c4baf1 Fix DELETE/UPDATE FOR PORTION OF with rules 7b22f15a015 Add psql tab completion for FOR PORTION OF clause 7ca8c942967 Fix FOR PORTION OF with non-updatable view columns 993a7aa0e4a Fix cross-leftover pollution in FOR PORTION OF insert triggers 7ac030d5b15 Require UPDATE permission on FOR PORTION OF column f0aedc7cb0e Small terminology fixes in comments 7d13b03a2e6 Fix FOR PORTION OF for inheritance children a272a58b942 Move FOR PORTION OF volatile check into planner a40fdf65886 Reject child partition FDWs in FOR PORTION OF bc3ae886a75 Forbid FOR PORTION OF with WHERE CURRENT OF c8d49ffb007 Forbid generated columns in FOR PORTION OF 5b5e99047ab Forbid FOR PORTION OF on views with INSTEAD OF triggers c58c83ce50c Fix RLS checks for FOR PORTION OF leftover rows 5454fe4a6e7 Test what BEFORE UPDATE triggers do to FOR PORTION OF 2a9541ddfd3 Deparse FOR PORTION OF using the range column's current name. fd92f74b91d Avoid RETURNING side effects for FOR PORTION OF leftovers. f3a116a26ff Enforce WITH CHECK OPTION on DELETE FOR PORTION OF leftovers c7e34c31e84 Fix error code for null FOR PORTION OF target 938f4f8f343 Fix assertion failures in DELETE FOR PORTION OF tuple routing f1940321687 Resolve untyped parameters in FOR PORTION OF FROM/TO bounds 98f6984e5c0 Don't evaluate the FOR PORTION OF target under EXPLAIN plus release notes entries. Discussion: https://www.postgresql.org/message-id/62bf70cc-dc33-4188-8070-a8c177bb61de%40eisentraut.org

Reject child partition FDWs in FOR PORTION OF

2026-06-27T17:36:51Z

We should defer validating FDW usage until after analysis. We have to guard against not just the topmost table, but also individual child partitions. Added the check to CheckValidResultRel, because it is called after looking up child partitions (accounting for pruning), but before the FDW can run a DirectModify update, which would bypass per-tuple executor work. Author: jian he Reported-by: Tom Lane Reviewed-by: Paul A. Jungwirth Discussion: https://www.postgresql.org/message-id/flat/CA%2BrenyUte0_UJsJiDJQi82oaBsMJn%3Dcct0Wn%3DvOqXtuDn%3DYYJA%40mail.gmail.com

Fix COPY FROM ON_ERROR SET_NULL with selective column list

2026-05-19T01:11:41Z

When using COPY FROM ... ON_ERROR SET_NULL with a selective column list, the domain_with_constraint array was incorrectly allocated based on the length of the target column list. While the array was populated sequentially, CopyFromTextLikeOneRow attempted to access it using the physical attribute index (attnum - 1). This mismatch caused out-of-bounds reads when targeting high-numbered columns, allowing NULL values to bypass NOT NULL domain checks and be silently inserted. Fix by allocating the array to match the total number of physical attributes (num_phys_attrs) and indexing via attnum - 1, bringing it into alignment with other per-column arrays in BeginCopyFrom. Author: SATYANARAYANA NARLAPURAM Reviewed-by: Jian He Reviewed-by: Chao Li Reviewed-by: Fujii Masao Discussion: https://postgr.es/m/CAHg+QDdej0c0gWJi2FnbirzhgzyZNPiTwC1P5B_-dSNCzq-91A@mail.gmail.com

Fix vicinity of tuple_insert to use uint32, not int, for options

2026-04-01T16:14:51Z

Oversight in commit 1bd6f22f43ac: I was way too optimistic about the compiler letting me know what variables needed to be updated, and missed a few of them. Clean it up. Author: Álvaro Herrera Reported-by: Chao Li Discussion: https://postgr.es/m/40E570EE-5A60-49D8-B8F7-2F8F2B7C8DFA@gmail.com

introduce CopyFormat, refactor CopyFormatOptions

2026-03-20T12:21:57Z

Currently, the COPY command format is determined by two boolean fields (binary, csv_mode) in CopyFormatOptions. This approach, while functional, isn't ideal for implementing other formats in the future. To simplify adding new formats, introduce a CopyFormat enum. This makes the code cleaner and more maintainable, allowing for easier integration of additional formats down the line. Author: Joel Jacobson Author: jian he Reviewed-by: Andrew Dunstan Discussion: https://postgr.es/m/CALvfUkBxTYy5uWPFVwpk_7ii2zgT07t3d-yR_cy4sfrrLU%3Dkcg%40mail.gmail.com Discussion: https://postgr.es/m/6a04628d-0d53-41d9-9e35-5a8dc302c34c@joeconway.com

Reduce header inclusions via execnodes.h

2026-03-16T13:34:57Z

Remove a bunch of #include lines from execnodes.h. Most of these requier suitable typedefs to be added, so that it still compiles standalone. In one case, the fix is to move a struct definition to the one .c file where it is needed. Also some light clean up in plannodes.h and genam.h, though not as extensive as in execnodes.h. Author: Álvaro Herrera Author: Andres Freund Discussion: https://postgr.es/m/202603131240.ihwqdxnj7w2o@alvherre.pgsql

Optimize COPY FROM (FORMAT {text,csv}) using SIMD.

2026-03-13T16:07:32Z

Presently, such commands scan the input buffer one byte at a time looking for special characters. This commit adds a new path that uses SIMD instructions to skip over chunks of data without any special characters. This can be much faster. To avoid regressions, SIMD processing is disabled for the remainder of the COPY FROM command as soon as we encounter a short line or a special character (except for end-of-line characters, else we'd always disable it after the first line). This is perhaps too conservative, but it could probably be made more lenient in the future via fine-tuned heuristics. Author: Nazir Bilal Yavuz Co-authored-by: Shinya Kato Reviewed-by: Ayoub Kazar Reviewed-by: Andrew Dunstan Reviewed-by: Neil Conway Reviewed-by: Greg Burd Tested-by: Manni Wood Tested-by: Mark Wong Discussion: https://postgr.es/m/CAOzEurSW8cNr6TPKsjrstnPfhf4QyQqB4tnPXGGe8N4e_v7Jig%40mail.gmail.com

Extend DomainHasConstraints() to optionally check constraint volatility

2026-03-12T22:04:16Z

Add an optional bool *has_volatile output parameter to DomainHasConstraints(). When non-NULL, the function checks whether any CHECK constraint contains a volatile expression. Callers that don't need this information pass NULL and get the same behavior as before. This is needed by a subsequent commit that enables the fast default optimization for domains with non-volatile constraints: we can safely evaluate such constraints once at ALTER TABLE time, but volatile constraints require a full table rewrite. Author: Jian He Reviewed-by: Tom Lane Reviewed-by: Andrew Dunstan Reviewed-by: Viktor Holmberg Discussion: https://postgr.es/m/CACJufxE_+iZBR1i49k_AHigppPwLTJi6km8NOsC7FWvKdEmmXg@mail.gmail.com

Add COPY (on_error set_null) option

2026-03-03T06:37:12Z

If ON_ERROR SET_NULL is specified during COPY FROM, any data type conversion errors will result in the affected column being set to a null value. A column's not-null constraints are still enforced, and attempting to set a null value in such columns will raise a constraint violation error. This applies to a column whose data type is a domain with a NOT NULL constraint. Author: Jian He Author: Kirill Reshke Reviewed-by: Fujii Masao Reviewed-by: Jim Jones Reviewed-by: "David G. Johnston" Reviewed-by: Yugo NAGATA Reviewed-by: torikoshia Reviewed-by: Masahiko Sawada Reviewed-by: Atsushi Torikoshi Reviewed-by: Matheus Alcantara Reviewed-by: Peter Eisentraut Discussion: https://www.postgresql.org/message-id/flat/CAKFQuwawy1e6YR4S%3Dj%2By7pXqg_Dw1WBVrgvf%3DBP3d1_aSfe_%2BQ%40mail.gmail.com

Use a bitmask for ExecInsertIndexTuples options

2026-02-17T16:59:45Z

... instead of passing a bunch of separate booleans. Also, rearrange the argument list in a hopefully more sensible order. Discussion: https://postgr.es/m/202602111846.xpvuccb3inbx@alvherre.pgsql Reviewed-by: Andres Freund Reviewed-by: Fabrízio de Royes Mello (older version)