| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(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 18:21:29 |
| Message-ID: | CA+U5nMJh4_Q1qxh-rbrAZh6jMs2omZ+-SsgR18GWM1uZQtB9qg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 19 September 2012 18:47, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-19 21:10:55 | pgsql: Put back AcceptInvalidationMessages calls in heap_openrv(_extend |
| Previous Message | Tom Lane | 2012-09-19 17:47:31 | Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-19 18:25:05 | Re: Removal of AcceptInvalidationMessages broke things |
| Previous Message | Noah Misch | 2012-09-19 18:17:42 | Re: Removal of AcceptInvalidationMessages broke things |