| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | "Mads(dot)Tandrup(at)schneider-electric(dot)com" <Mads(dot)Tandrup(at)schneider-electric(dot)com> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Streaming replication with sync slave, but disconnects due to missing WAL segments |
| Date: | 2013-06-06 16:32:55 |
| Message-ID: | CAMkU=1zhrNG2nVuVf_x1yiFq6F=chJ2VWARUxoWVLHhzHFf8pQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jun 5, 2013 at 11:26 PM, <Mads(dot)Tandrup(at)schneider-electric(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | François Beausoleil | 2013-06-06 16:37:29 | Slave promotion failure |
| Previous Message | François Beausoleil | 2013-06-06 15:40:13 | User postgres unable to revoke privileges? |