From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Ron <ronljohnsonjr@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Old WAL files under pg_xlog not getting delete
Date: Wed, 30 Jan 2019 21:00:15 -0300
Message-ID: <201901310000.fkapsf6clz5s@alvherre.pgsql> (raw)
In-Reply-To: <aea0796a-9b55-aa75-4ad3-5377fc03e240@gmail.com>
On 2019-Jan-30, Ron wrote:
> Plus the ".", ".." and archive_status directories, and lost+found if pg_xlog
> is it's own partition. That's four of the unknown six. Add a .backup file
> or two and all 506 files are accounted for.
Hmm ... I would recommend to keep the xlog files in a subdir, not the
root of the filesystem. So the lost+found would be, at the most, a
sibling of pg_xlog, not inside it. Otherwise, it seems too easy to get
in trouble if for whatever reason the filesystem is not mounted, your
database starts writing files in it, and the filesystem is mounted
later. Whatever files got written before mounting would be misteriously
"missing", and few people think to unmount the FS to see if they are in
the underlying filesystem.
Then again, if you read this advice then you're safe because next time
this happens to you, you'll remember to unmount to check, so you can
safely ignore me. Go figure.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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-admin@postgresql.org
Cc: alvherre@2ndquadrant.com, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Old WAL files under pg_xlog not getting delete
In-Reply-To: <201901310000.fkapsf6clz5s@alvherre.pgsql>
* 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