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:50:16 +0000 (08:50 +0900)
commit1a6690016604bfc2c61fef867e8ddbebf4d21428
tree189122616df5d8cb45e24e68cfeccf4f335d26c0
parent3a01610529722ac711d7905255b34a78e55b6905
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