Re: [GENERAL] Recovery Data Cant Be!!!

2003-11-07 Thread Edwin Quijada
How can I do from postgresql.conf? From: Bruce Momjian <[EMAIL PROTECTED]> To: Tom Lane <[EMAIL PROTECTED]> CC: Edwin Quijada <[EMAIL PROTECTED]>,[EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [GENERAL] Recovery Data Cant Be!!! Date: Fri, 7 Nov 2003 16:31:43 -0500 (ES

Re: [GENERAL] Recovery Data Cant Be!!!

2003-11-07 Thread Edwin Quijada
comun" *---* From: Tom Lane <[EMAIL PROTECTED]> To: Bruce Momjian <[EMAIL PROTECTED]> CC: Edwin Quijada <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [GENERAL] Recovery Data Cant Be!!! Date: Fri, 07 Nov 2003 16:29:18 -0500 Bru

Re: [GENERAL] Recovery Data Cant Be!!!

2003-11-07 Thread Edwin Quijada
ROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [GENERAL] Recovery Data Cant Be!!! Date: Fri, 07 Nov 2003 16:29:18 -0500 Bruce Momjian <[EMAIL PROTECTED]> writes: > Edwin Quijada wrote: >> Where set zero_damaged_pages ?? > You can't set it from postgresq

Re: [GENERAL] Recovery Data Cant Be!!!

2003-11-07 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Oh, I never realized it would work with damage that severe. I'm not sure it will, but it's his best shot. Actually, I think there is a TODO item here. In most cases where a page is being touched during WAL replay, we have a complete image of the page s

Re: [GENERAL] Recovery Data Cant Be!!!

2003-11-07 Thread scott.marlowe
You're likely looking for pgfsck: http://svana.org/kleptog/pgsql/pgfsck.html Strong medicine, please backup your $PGDATA directory before playing there, as you might wind up breaking things. What's the exact error message in your logs when the database won't start up? The problem you're see

Re: [GENERAL] Recovery Data Cant Be!!!

2003-11-07 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Edwin Quijada wrote: >> Where set zero_damaged_pages ?? > You can't set it from postgresql.conf. Sure you can, and in fact that's the only place that will work for Edwin's problem. He hasn't *got* a psql session, because postmaster startup is failing.

Re: [GENERAL] Recovery Data Cant Be!!!

2003-11-07 Thread Bruce Momjian
Edwin Quijada wrote: > > Where set zero_damaged_pages ?? You can't set it from postgresql.conf. It has to be set in your psql session: SET zero_damaged_pages = true; -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-100

Re: [GENERAL] Recovery Data Cant Be!!!

2003-11-07 Thread Edwin Quijada
<[EMAIL PROTECTED]> To: Edwin Quijada <[EMAIL PROTECTED]> CC: <[EMAIL PROTECTED]> Subject: Re: [GENERAL] Recovery Data Cant Be!!! Date: Fri, 7 Nov 2003 13:29:57 -0700 (MST) You're likely looking for pgfsck: http://svana.org/kleptog/pgsql/pgfsck.html Strong medicine, please back

Re: [GENERAL] Recovery Data Cant Be!!!

2003-11-07 Thread Edwin Quijada
comun" *---* From: Jeff <[EMAIL PROTECTED]> To: "Edwin Quijada" <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Subject: Re: [GENERAL] Recovery Data Cant Be!!! Date: Fri, 7 Nov 2003 13:25:18 -0500 On Fri, 07 Nov 2003 18:08:32 + "Edwin Quijada" <[EMAIL PROTECT

Re: [GENERAL] Recovery Data Cant Be!!!

2003-11-07 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Edwin Quijada wrote: > >> Where set zero_damaged_pages ?? > > > You can't set it from postgresql.conf. > > Sure you can, and in fact that's the only place that will work for > Edwin's problem. He hasn't *got* a psql session, because