| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | "Akash Kodibail" <akash(dot)kodibail(at)onmobile(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Postgres Server crashed |
| Date: | 2011-10-10 19:02:54 |
| Message-ID: | 4E92FB0E0200002500041CE9@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>
>> And normal maintenance may be viewing newer data as old, due to
>> transaction wrap-around from the old pg_control file, and
>> removing it as part of normal cleanup. So you may have destroyed
>> some of your more recent data by doing that.
>
> At this point, once you have a backup, would you deploy
> pg_resetxlog?
That's what I was thinking. I shudder to think what autovacuum may
have done while running with the old pg_control file; but I don't
know what else to do at this juncture.
Anyone else have a better idea?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2011-10-10 19:10:52 | Re: Postgres Server crashed |
| Previous Message | Scott Marlowe | 2011-10-10 18:28:34 | Re: Postgres Server crashed |