On Tuesday 11 September 2001 06:04, Nick Fankhauser wrote:
> Hi all-
>
> I caused a crash by filling up the filesystem that pg_xlog lives on whilst
> doing a vacuum analyze. When I looked at the remains, there were 3 WAL
> files out there & no space left.
>
> I tried simply restarting (/etc/init.d
Hi all-
I caused a crash by filling up the filesystem that pg_xlog lives on whilst
doing a vacuum analyze. When I looked at the remains, there were 3 WAL files
out there & no space left.
I tried simply restarting (/etc/init.d/postgresql start) in the hopes that
the mess would get cleaned, but wi
This depends on the type of update. If you commit the transaction
regularly, files will be re-used. On the other hand, if you commit the
transaction at the end like what the COPY command (pg_dump) does, extra WAL
files will be created as needed (even though the limit has been reached).
Regards
> You can try running pg_resetxlog (situated in the contrib directory in the
> source). It will reset the wal files and will allow you to restart the
> postmaster.
I just did an initdb as suggested by Randy since the data was easy to
recreate, but this is good to know as a fallback for future si
You can try running pg_resetxlog (situated in the contrib directory in the
source). It will reset the wal files and will allow you to restart the
postmaster. It is not the recommended way but I used in in dire
emergencies and it worked.
Normally, when you fill up the drive because of WALs, you
ers.home.net/rthall3
>
> - Original Message -
> From: "Nick Fankhauser" <[EMAIL PROTECTED]>
> To: "pgsql-admin" <[EMAIL PROTECTED]>
> Sent: Tuesday, September 11, 2001 7:16 AM
> Subject: [ADMIN] Can't get postmaster to restart after
: http://members.home.net/rthall3
- Original Message -
From: "Nick Fankhauser" <[EMAIL PROTECTED]>
To: "pgsql-admin" <[EMAIL PROTECTED]>
Sent: Tuesday, September 11, 2001 7:16 AM
Subject: [ADMIN] Can't get postmaster to restart after removing WAL file
Hi all-
I caused a crash by filling up the filesystem that pg_xlog lives on whilst
doing a vacuum analyze. When I looked at the remains, there were 3 WAL files
out there & no space left.
I tried simply restarting (/etc/init.d/postgresql start) in the hopes that
the mess would get cleaned, but wi
