pgsql: Prevent (auto)vacuum from truncating first page of populated mat
Prevent (auto)vacuum from truncating first page of populated matview.
Per report from Fujii Masao, with regression test using his example.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/b69ec7cc990fd8da75ed4c232899503217d7b9ae
Modified Files
--------------
src/backend/commands/vacuumlazy.c | 6 ++++++
src/test/regress/expected/matview.out | 20 ++++++++++++++++++++
src/test/regress/sql/matview.sql | 12 ++++++++++++
3 files changed, 38 insertions(+), 0 deletions(-)
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
Kevin Grittner <kgrittn@postgresql.org> writes:
Prevent (auto)vacuum from truncating first page of populated matview.
Per report from Fujii Masao, with regression test using his example.
What happens when VACUUM is applied to an unscannable matview?
I remain of the opinion that this is a band-aid on an unsustainable
design, regardless of such minor points.
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers