pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Huxton <dev@archonet.com>
Cc: Shea,Dan [CIS] <Dan.Shea@ec.gc.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: after using pg_resetxlog, db lost
Date: Tue, 22 Jun 2004 16:25:19 -0400
Message-ID: <21594.1087935919@sss.pgh.pa.us> (raw)
In-Reply-To: <40D890F3.8090208@archonet.com>
References: <644D07D3D59D8F408CD01AC2F833D8C62B9209@cisxa.cmc.int.ec.gc.ca>
	<21115.1087932963@sss.pgh.pa.us>
	<40D890F3.8090208@archonet.com>

Richard Huxton <dev@archonet.com> writes:
> Tom Lane wrote:
>> This could be repaired by doing
>> pg_resetxlog with a more appropriate initial transaction ID, but
>> figuring out what that value should be is not easy :-(

> Tom - would there be any value in adding this to a pg_dump?

Possibly.  CVS tip pg_dump has been changed to not output OIDs by
default, as a result of gripes from people who wanted to be able to
"diff" dumps from different servers and not have the diff cluttered
by irrelevant OID differences.  But a single header line showing
current XID and OID values doesn't seem like it would be a big problem.
We could put current timestamp there too, which was another recent topic
of discussion.

Bring it up on pghackers and see if anyone has an objection...

			regards, tom lane



view thread (9+ messages)  latest in thread

Message-ID: <21594.1087935919@sss.pgh.pa.us>
Permalink:  ../21594.1087935919@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/21594.1087935919@sss.pgh.pa.us

 · 

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-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, dev@archonet.com, Dan.Shea@ec.gc.ca
  Subject: Re: after using pg_resetxlog, db lost
  In-Reply-To: <21594.1087935919@sss.pgh.pa.us>

* 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