Hello-
I currently have a 1.4 TB database (pg version 7.4.8) that is
experiencing transaction id wraparound. I plan to pg_dump the database
and initdb and reload. I may reload into an 8.1 database at this
time.
I am curious how to make sure that I indeed get all the data out of the
tables from
On Mon, May 15, 2006 at 11:44:01AM -0700, Michael L. Boscia wrote:
Hello-
I currently have a 1.4 TB database (pg version 7.4.8) that is experiencing
transaction id wraparound. I plan to pg_dump the database and initdb and
reload. I may reload into an 8.1 database at this time.
I am
On Mon, 2006-05-15 at 13:48, Martijn van Oosterhout wrote:
On Mon, May 15, 2006 at 11:44:01AM -0700, Michael L. Boscia wrote:
Hello-
I currently have a 1.4 TB database (pg version 7.4.8) that is experiencing
transaction id wraparound. I plan to pg_dump the database and initdb and
On Mon, May 15, 2006 at 08:48:54PM +0200, Martijn van Oosterhout wrote:
Vacuum will make anything that disappeared by wraparound in the last
billion transactions reappear, so a databasewide vacuum should solve
all your problems, no need to dump...
Also, for future reference. If you have a lot
Michael L. Boscia [EMAIL PROTECTED] writes:
My current plan is selectively dump a portion of the data (most current,
organized in tables by date ex xxx_2006_may) and reload. I plan to vaccuum
each table before dumping. Please warn me if this is not enough. Any
assistance is greatly
Martijn van Oosterhout kleptog@svana.org writes:
Vacuum will make anything that disappeared by wraparound in the last
billion transactions reappear, so a databasewide vacuum should solve
all your problems, no need to dump...
Oh, I had forgotten about that. Did we establish that 7.4.* works
On 5/15/06, Scott Marlowe [EMAIL PROTECTED] wrote:
On Mon, 2006-05-15 at 13:48, Martijn van Oosterhout wrote:
On Mon, May 15, 2006 at 11:44:01AM -0700, Michael L. Boscia wrote:
Hello-
I currently have a 1.4 TB database (pg version 7.4.8) that is experiencing
transaction id wraparound.
On Mon, 2006-05-15 at 14:07, Michael L. Boscia wrote:
On 5/15/06, Scott Marlowe [EMAIL PROTECTED] wrote:
This is one of those rare instances when I'd shut down the server and
take a file system backup if I could. However, at 1.4 TB, that might be
a bit difficult... :)
What do I do with
On Mon, May 15, 2006 at 03:04:47PM -0400, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
Vacuum will make anything that disappeared by wraparound in the last
billion transactions reappear, so a databasewide vacuum should solve
all your problems, no need to dump...
Oh, I
And I just demonstrated it on a test 7.4.7 database here (Debian
7.4.7-6 to be precise).
test=# select ctid, xmin, xmax, cmin, cmax, * from test;
ctid |xmin| xmax | cmin | cmax | x
---++--+--+--+---
(0,1) |541 |0 |0 |0 | 1
(0,2) |
10 matches
Mail list logo
