Re: Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied
Date: 2014-05-16 19:39:26
Message-ID: 5376696E.2040306@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/16/2014 08:11 PM, David G Johnston wrote:
> Can we simply backup the non-data parts of $PGDATA first then move onto the
> data-parts? For the files that we'd be dealing with it would be
> sufficiently quick to just try and fail, immediately, then check for all
> possible preconditions first. The main issue seems to be the case where the
> 2TB of data get backed-up and then a small 1k file blows away all that work.
> Lets do those 1k files first.

You'll still need to distinguish "data" and "non-data" parts somehow.
One idea would be to backup any files in the top directory first, before
recursing into the subdirectories. That would've caught the OP's case,
and probably many other typical cases where you drop something
unexpected into $PGDATA. You could still have something funny nested
deep in the data directory, but that's much less common.

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-05-16 19:44:20 Re: btree_gist macaddr valgrind woes
Previous Message Tom Lane 2014-05-16 19:36:29 Re: btree_gist macaddr valgrind woes