diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-08-19 12:12:35 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-08-19 12:12:35 -0400 |
| commit | 4649003933522282f03643c5a50fd2eb2a31a783 (patch) | |
| tree | af235958fc887902a5aeea4365dea223c461ebee /src/backend/regex/regcomp.c | |
| parent | 18914f24ec6e704e81a5528cf09f3d54b23ef12b (diff) | |
| download | postgresql-4649003933522282f03643c5a50fd2eb2a31a783.tar.gz postgresql-4649003933522282f03643c5a50fd2eb2a31a783.zip | |
Avoid trying to lock OLD/NEW in a rule with FOR UPDATE.
transformLockingClause neglected to exclude the pseudo-RTEs for
OLD/NEW when processing a rule's query. This led to odd errors
or even crashes later on. This bug is very ancient, but it's
not terribly surprising that nobody noticed, since the use-case
for SELECT FOR UPDATE in a non-view rule is somewhere between
thin and non-existent. Still, crashing is not OK.
Per bug #17151 from Zhiyong Wu. Thanks to Masahiko Sawada
for analysis of the problem.
Discussion: https://postgr.es/m/17151-c03a3e6e4ec9aadb@postgresql.org
Diffstat (limited to 'src/backend/regex/regcomp.c')
0 files changed, 0 insertions, 0 deletions