Re: Streaming replication with sync slave, but disconnects due to missing WAL segments - Mailing list pgsql-general

From Jeff Janes
Subject Re: Streaming replication with sync slave, but disconnects due to missing WAL segments
Date
Msg-id CAMkU=1zhrNG2nVuVf_x1yiFq6F=chJ2VWARUxoWVLHhzHFf8pQ@mail.gmail.com
Whole thread Raw
In response to Re: Streaming replication with sync slave, but disconnects due to missing WAL segments  (Mads.Tandrup@schneider-electric.com)
Responses Re: Streaming replication with sync slave, but disconnects due to missing WAL segments  (Mads.Tandrup@schneider-electric.com)
List pgsql-general
On Wed, Jun 5, 2013 at 11:26 PM, <Mads.Tandrup@schneider-electric.com> wrote:
Hi

Thanks for your reply. Do you know of any options that I could give pg_dump/psql to avoid creating one big transaction? I'm using the plain text format for pg_dump.


For the plain text format, it is already not one big transaction, unless you specify to -1 to the psql.  However, the load of any individual table will still be a single transaction, so for a very large table it will still be a very long transaction.  

Using pg_dump for --inserts could get around this, but it would probably be better to fix the fundamental problem by increasing wal_keep_segments or something of that nature.

Cheers,

Jeff

pgsql-general by date:

Previous
From: François Beausoleil
Date:
Subject: User postgres unable to revoke privileges?
Next
From: François Beausoleil
Date:
Subject: Slave promotion failure