Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "devrim(at)gunduz(dot)org" <devrim(at)gunduz(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.
Date: 2012-09-19 17:47:31
Message-ID: 1255.1348076851@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2012-09-19 18:21:29 Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.
Previous Message Tom Lane 2012-09-19 14:46:40 pgsql: Update time zone data files to tzdata release 2012f.

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2012-09-19 18:17:42 Re: Removal of AcceptInvalidationMessages broke things
Previous Message Tom Lane 2012-09-19 17:26:37 Re: Invalid optimization of VOLATILE function in WHERE clause?