From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Ghislain ROUVIGNAC <ghr(at)sylob(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Portworx snapshots |
Date: | 2018-10-30 15:21:36 |
Message-ID: | 20181030152136.GQ4184@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greetings,
* Laurenz Albe (laurenz(dot)albe(at)cybertec(dot)at) wrote:
> Stephen Frost wrote:
> > The downside with any snapshot-style approach is that it means that when
> > you have a failure, you have to go through and replay all the WAL since
> > the last checkpoint, which is single-threaded and can take a large
> > amount of time.
> >
> > When doing your testing, I'd strongly recommend that you have a large
> > max_wal_size, run a large pgbench which writes a lot of data, and see
> > how long a failover takes with this system.
>
> Then "checkpoint_timeout" should also be large, right?
Having a larger checkpoint timeout would also show that this method of
failover runs the risk of there being a very long time required between
when the failure is detected and when the new primary is online.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2018-10-30 15:26:27 | Re: Portworx snapshots |
Previous Message | Kathleen Emerson | 2018-10-30 14:57:34 | pg_stat_all_tables.last_vacuum not always correct. |