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 | 0c13ee198f0d690765550fc1c694f9191e9785d6 (patch) | |
| tree | 04b75d3c003454d898addfbd4341fdf72d64961c /src/backend/regex/regexport.c | |
| parent | eb2f59b34e256a34f65518d01ebe7c282052ae4e (diff) | |
| download | postgresql-0c13ee198f0d690765550fc1c694f9191e9785d6.tar.gz postgresql-0c13ee198f0d690765550fc1c694f9191e9785d6.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/regexport.c')
0 files changed, 0 insertions, 0 deletions