From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: emergency outage requiring database restart |
Date: | 2016-10-25 19:31:25 |
Message-ID: | 1671.1477423885@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> What if the subsequent dataloss was in fact a symptom of the first
> outage? Is in theory possible for data to appear visible but then be
> eaten up as the transactions making the data visible get voided out by
> some other mechanic? I had to pull a quick restart the first time and
> everything looked ok -- or so I thought. What I think was actually
> happening is that data started to slip into the void. It's like
> randomly sys catalogs were dropping off. I bet other data was, too. I
> can pull older backups and verify that. It's as if some creeping xmin
> was snuffing everything out.
Might be interesting to look at age(xmin) in a few different system
catalogs. I think you can ignore entries with age = 2147483647;
those should be frozen rows. But if you see entries with very large
ages that are not that, it'd be suspicious.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2016-10-25 20:08:39 | Re: emergency outage requiring database restart |
Previous Message | Merlin Moncure | 2016-10-25 19:13:39 | Re: emergency outage requiring database restart |