pgsql: Always make a BufferAccessStrategy for ANALYZE - Mailing list pgsql-committers

From David Rowley
Subject pgsql: Always make a BufferAccessStrategy for ANALYZE
Date
Msg-id E1pkDd0-001Zi7-Vq@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Always make a BufferAccessStrategy for ANALYZE

32fbe0239 changed things so we didn't bother allocating the
BufferAccessStrategy during VACUUM (ONLY_DATABASE_STATS); and VACUUM
(FULL), however, it forgot to consider that VACUUM (FULL, ANALYZE) is a
possible combination.  That change would have resulted in such a command
allowing ANALYZE to make full use of shared buffers, which wasn't
intended, so fix that.

Reported-by: Melanie Plageman
Discussion: https://postgr.es/m/CAAKRu_bJRKe+v_=OqwC+5sA3j5qv8rqdAwy3+yHaO3wmtfrCRg@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/bccd6908ca82c6cba0c76b669bc81fc9f3fb60cd

Modified Files
--------------
src/backend/commands/vacuum.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Fix row tracking in pg_stat_statements with extended query proto
Next
From: Andres Freund
Date:
Subject: pgsql: Use ExtendBufferedRelTo() in {vm,fsm}_extend()