diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-06-18 18:00:09 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-06-18 18:00:09 -0400 |
| commit | b7e3a440775b6595ede98878f8a971a92364cf4d (patch) | |
| tree | 350a3df036bfb145af050731fa04b7aa641a17bd /src/tutorial/complex.source | |
| parent | f172438ef6ff7fa374edeaee423241410c97566c (diff) | |
Fix misbehavior of DROP OWNED BY with duplicate polroles entries.
Ordinarily, a pg_policy.polroles array wouldn't list the same role
more than once; but CREATE POLICY does not prevent that. If we
perform DROP OWNED BY on a role that is listed more than once,
RemoveRoleFromObjectPolicy either suffered an assertion failure
or encountered a tuple-updated-by-self error. Rewrite it to cope
correctly with duplicate entries, and add a CommandCounterIncrement
call to prevent the other problem.
Per discussion, there's other cleanup that ought to happen here,
but this seems like the minimum essential fix.
Per bug #17062 from Alexander Lakhin. It's been broken all along,
so back-patch to all supported branches.
Discussion: https://postgr.es/m/17062-11f471ae3199ca23@postgresql.org
Diffstat (limited to 'src/tutorial/complex.source')
0 files changed, 0 insertions, 0 deletions