Optimize query cache invalidation for ALTER ROLE.
authorTatsuo Ishii <ishii@postgresql.org>
Tue, 22 Oct 2024 22:47:37 +0000 (07:47 +0900)
committerTatsuo Ishii <ishii@postgresql.org>
Tue, 22 Oct 2024 23:48:51 +0000 (08:48 +0900)
commit329b5da3f8c76df9723d78727ee4f41182c47b3e
treefd89b425554ecd8ddcdcf3404157463335a12490
parentc5c1ca6b37fdc0b25b5507abfbdadd40bc2e81a7
Optimize query cache invalidation for ALTER ROLE.

Commit 6b7d585eb1c693e4ffb5b8e6ed9aa0f067fa1b89 invalidates query
cache if any ALTER ROLE/USER statement is used. Actually this is an
overkill. Because following queries do not affect the privilege of the
role.

- ALTER ROLE user WITH [ENCRYPTED] PASSWORD
- ALTER ROLE user WITH CONNECTION LIMIT

So do not invalidate query cache if those commands are used.

Backpatch-through: v4.1
Discussion: https://www.pgpool.net/pipermail/pgpool-hackers/2024-October/004532.html
doc.ja/src/sgml/memcache.sgml
doc/src/sgml/memcache.sgml
src/protocol/CommandComplete.c
src/test/regression/tests/006.memqcache/expected.n
src/test/regression/tests/006.memqcache/expected.r
src/test/regression/tests/006.memqcache/expected.s
src/test/regression/tests/006.memqcache/test.sh