or all the support.
Next destination postgres documentation. :-)
Many thanks and Regards,
Akash.
-Original Message-
From: Akash Kodibail
Sent: Tuesday, October 11, 2011 1:02 AM
To: 'Scott Marlowe'
Cc: Kevin Grittner; [email protected]
Subject: RE: [ADMIN] Postgres Server c
On Mon, Oct 10, 2011 at 2:59 PM, Kevin Grittner
wrote:
> Akash Kodibail wrote:
>
>> Can you please help me out in the options that might have to be
>> set for pg_resetxlog.
>
> It should normally be able to calculate what it needs if you just
> point it at the data directory. I would run it with
Akash Kodibail wrote:
> Can you please help me out in the options that might have to be
> set for pg_resetxlog.
It should normally be able to calculate what it needs if you just
point it at the data directory. I would run it with the -n (no
operation) flag first, to see what it plans to do.
[email protected]
Subject: Re: [ADMIN] Postgres Server crashed
On Mon, Oct 10, 2011 at 1:13 PM, Akash Kodibail
wrote:
> 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-requi
On Mon, Oct 10, 2011 at 1:13 PM, Akash Kodibail
wrote:
> 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.
With PITR you
: Kevin Grittner [mailto:[email protected]]
Sent: Tuesday, October 11, 2011 12:33 AM
To: Scott Marlowe
Cc: Akash Kodibail; [email protected]
Subject: Re: [ADMIN] Postgres Server crashed
Scott Marlowe wrote:
> Kevin Grittner wrote:
>
>> And normal maintenance ma
Scott Marlowe wrote:
> Kevin Grittner 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.
>
>
On Mon, Oct 10, 2011 at 11:17 AM, Kevin Grittner
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.
nt sure has taught me a lesson. pg_clog and pg_xlog are untouched.
Thanks and Regards,
Akash.
-Original Message-
From: Kevin Grittner [mailto:[email protected]]
Sent: Monday, October 10, 2011 10:47 PM
To: Akash Kodibail; [email protected]
Subject: Re: [ADMIN] Postgres
kash Kodibail wrote:
> Lately the postgres server crashed due to space constraints,
The very first thing to do is to copy the entire directory structure
for the database cluster to somewhere you can keep it safe until the
problem has been resolved. If you have not yet done so, I strongly
reco
Hi All,
I am a noob in database field.
Lately the postgres server crashed due to space constraints, pg_control file
got lost and the server wouldn't start. Had a old pg_control file placed in
$PGDATA/global/ path.
I was able to start the server, however, the data seems to be a very old one
(2
11 matches
Mail list logo
