Re: pgsql: Prevent (auto)vacuum from truncating first page of populated mat

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Grittner <kgrittn(at)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Prevent (auto)vacuum from truncating first page of populated mat
Date: 2013-05-03 03:36:32
Message-ID: 10950.1367552192@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Kevin Grittner <kgrittn(at)postgresql(dot)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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2013-05-03 15:11:48 Re: [COMMITTERS] pgsql: Revert "pg_ctl: Add idempotent option"
Previous Message Bruce Momjian 2013-05-02 23:14:51 pgsql: 9.3 release notes: suggested improvements from Jeff Janes and J