mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-10 17:59:28 +02:00
Previously, relation range table entries used a single Bitmapset field representing which columns required either UPDATE or INSERT privileges, despite the fact that INSERT and UPDATE privileges are separately cataloged, and may be independently held. As statements so far required either insert or update privileges but never both, that was sufficient. The required permission could be inferred from the top level statement run. The upcoming INSERT ... ON CONFLICT UPDATE feature needs to independently check for both privileges in one statement though, so that is not sufficient anymore. Bumps catversion as stored rules change. Author: Peter Geoghegan Reviewed-By: Andres Freund |
||
---|---|---|
.. | ||
expected | ||
sql | ||
.gitignore | ||
database.c | ||
dml.c | ||
hooks.c | ||
label.c | ||
launcher | ||
Makefile | ||
proc.c | ||
relation.c | ||
schema.c | ||
selinux.c | ||
sepgsql-regtest.te | ||
sepgsql.h | ||
sepgsql.sql.in | ||
test_sepgsql | ||
uavc.c |