Re: pg_basebackup error

Nevermind :) There was a large backup.sql file on my master from a past
operation.

On Sun, Apr 14, 2013 at 11:11 AM, Armand du Plessis <adp(at)bank(dot)io> wrote:

> I'm busy preparing a server to act as a streaming replication slave. When
> using the pg_basebackup to get the initial setup done I run into the
> following error after it's almost complete:
>
> bash-4.1$ pg_basebackup -v -P -c fast -h master -U replica -D
> /raiddrive/pgdata
> 185107020/227631618 kB (100%), 1/1 tablespace
>
> pg_basebackup: could not get transaction log end position from server:
> FATAL: archive member "backup.sql" too large for tar format
>
> Initially I specified -F t with -z as I assumed that would speed up the
> transfer but had a similar error. This time with the default options in
> plain format I'm getting the same error which I find strange.
>
> By default full_page_writes is disabled on my master, I've seen references
> that it needs to be on but also other info that it would be forced on
> during the backup process.
>
> The error message seems pretty explicit about trying to tar something so
> not sure whether the full_page_writes is having an effect here.
>
> Regards,
>
> Armand
>
>
>
>
>