aboutsummaryrefslogtreecommitdiff
path: root/src/common/file_utils.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-05-21 15:02:07 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-05-21 15:02:07 -0400
commit77e3204ecbf15ab5dfd295bbc66eeeec4d9ade19 (patch)
treed05a40262c896f41b3cc33712a002e54835b5c96 /src/common/file_utils.c
parentd18ee6f92d9a22b4fae57f515797b2196bf385c7 (diff)
downloadpostgresql-77e3204ecbf15ab5dfd295bbc66eeeec4d9ade19.tar.gz
postgresql-77e3204ecbf15ab5dfd295bbc66eeeec4d9ade19.zip
Fix usage of "tableoid" in GENERATED expressions.
We consider this supported (though I've got my doubts that it's a good idea, because tableoid is not immutable). However, several code paths failed to fill the field in soon enough, causing such a GENERATED expression to see zero or the wrong value. This occurred when ALTER TABLE adds a new GENERATED column to a table with existing rows, and during regular INSERT or UPDATE on a foreign table with GENERATED columns. Noted during investigation of a report from Vitaly Ustinov. Back-patch to v12 where GENERATED came in. Discussion: https://postgr.es/m/CAM_DEiWR2DPT6U4xb-Ehigozzd3n3G37ZB1+867zbsEVtYoJww@mail.gmail.com
Diffstat (limited to 'src/common/file_utils.c')
0 files changed, 0 insertions, 0 deletions