WAL oddities (8.0.3)

From: Rod Taylor <pg(at)rbt(dot)ca>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: WAL oddities (8.0.3)
Date: 2005-06-30 16:10:43
Message-ID: 1120147843.86404.133.camel@home
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

First, are WAL files not allowed to end in FF?

I was looking at the logs and it jumps straight from
0000000100000194000000FE to 000000010000019500000000.

Yet other times it seems to end in an F: 0000000100000194000000EF.

Second, we have log archival enabled and the system it was archiving to
was unavailable. Once that system was brought back, everything resumed
appropriately and the files were copied over.

However, now I'm left with a pg_xlog directory that is about 7 GB in
size. All of the files but the most recent has a corresponding
archive_status/$FILE.done file. Will PostgreSQL eventually remove most
of these unnecessary files or am I stuck with them?

--

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2005-06-30 16:29:40 Re: Checkpoint cost, looks like it is WAL/CRC
Previous Message Michael Glaesemann 2005-06-30 16:01:27 Re: Moving sequences to another schema