Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries. - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.
Date
Msg-id CA+U5nMJh4_Q1qxh-rbrAZh6jMs2omZ+-SsgR18GWM1uZQtB9qg@mail.gmail.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 19 September 2012 18:47, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> BTW, what should our advice be for recovering from corruption due to
> this bug?  As far as the btree and GIN problems go, we can tell people
> that REINDEX will fix it.  And in 9.1, you don't really need to worry
> about the visibility map being bad.  But what do you do in 9.2, if
> you have a bad visibility map?  Is there any fix short of VACUUM FULL?

SET vacuum_freeze_table_age = 0;
VACUUM;

I'm writing the full notes out now.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Removal of AcceptInvalidationMessages broke things
Next
From: Tom Lane
Date:
Subject: Re: Removal of AcceptInvalidationMessages broke things