pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Akash Kodibail <akash.kodibail@onmobile.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Postgres Server crashed
Date: Tue, 11 Oct 2011 00:43:48 +0530
Message-ID: <04DA5C9AF2453F44ACD4541A08EFE9832D0CF8EF30@MUSCA.onmobile.com> (raw)
In-Reply-To: <4E92FB0E0200002500041CE9@gw.wicourts.gov>
References: <04DA5C9AF2453F44ACD4541A08EFE9832D0CF8EE87@MUSCA.onmobile.com>
	<4E92E24E0200002500041CCA@gw.wicourts.gov>
	<CAOR=d=3uChiqSyre1MbCGgEdMU9u1Xh_DqbJgKBD3vCrqJwBug@mail.gmail.com>
	<4E92FB0E0200002500041CE9@gw.wicourts.gov>

I was hopeful of restoring the data from data files in $PGDATA path. I read this article about PITR using the recovery.conf, But I am not aware of the pre-requisites and not entirely sure about the concept beneath this.

Would it not be possible?

Regards,
Akash.

-----Original Message-----
From: Kevin Grittner [mailto:Kevin.Grittner@wicourts.gov]
Sent: Tuesday, October 11, 2011 12:33 AM
To: Scott Marlowe
Cc: Akash Kodibail; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Postgres Server crashed

Scott Marlowe <scott.marlowe@gmail.com> wrote:
> Kevin Grittner <Kevin.Grittner@wicourts.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

DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.



view thread (11+ messages)  latest in thread

Message-ID: <04DA5C9AF2453F44ACD4541A08EFE9832D0CF8EF30@MUSCA.onmobile.com>
Permalink:  ../04DA5C9AF2453F44ACD4541A08EFE9832D0CF8EF30@MUSCA.onmobile.com/
Also on:    postgresql.org/message-id/04DA5C9AF2453F44ACD4541A08EFE9832D0CF8EF30@MUSCA.onmobile.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: akash.kodibail@onmobile.com, Kevin.Grittner@wicourts.gov, scott.marlowe@gmail.com
  Subject: Re: Postgres Server crashed
  In-Reply-To: <04DA5C9AF2453F44ACD4541A08EFE9832D0CF8EF30@MUSCA.onmobile.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox