From: | Armand du Plessis <adp(at)bank(dot)io> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | pg_basebackup error |
Date: | 2013-04-14 18:11:02 |
Message-ID: | CANf99sXgDRC7_Zr2hZmFqGiJNCNMJmxJjP3Y8TxH0VhuAdmymA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Armand du Plessis | 2013-04-14 19:07:17 | Re: pg_basebackup error |
Previous Message | Scott Marlowe | 2013-04-12 23:06:15 | Re: [PERFORM] Recommended Swap space |