| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Ekaterina Amez <ekaterina(dot)amez(at)zunibal(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Questions about how to streaming replication (pg 9.2) |
| Date: | 2020-01-21 16:47:46 |
| Message-ID: | 906c97b626f5252bd19af543dafbe2e40ed5d451.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2020-01-21 at 11:18 +0100, Ekaterina Amez wrote:
[about wal_keep_segments]
> I'm not sure how to figure this value . Of course I could use a big
> value and forget, but as the server is running out of space I'd like to
> adjust it so there is (almost) no waste of space. This is why I began to
> think about wal archiving, though it seems a bit more complicated.
See how many WAL files are generated in a day.
If you set wal_keep_segments to that value, the standby will be
able to survive a down time of a day.
If you don't need to cater for that much down time, use a smaller value.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | M Tarkeshwar Rao | 2020-01-22 05:58:34 | After restart of our C++(postgres client) which is running in the kubernetes pod, connection is getting hanged. |
| Previous Message | Nicola Contu | 2020-01-21 16:14:15 | Re: ERROR: too many dynamic shared memory segments |