| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Shukla, Pranjal" <pshukla(at)akamai(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Query on WAL Optimization and Streaming Replication |
| Date: | 2022-03-17 14:38:31 |
| Message-ID: | 3ce9de9d04a013c718d174e00cb91bb896591b2a.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2022-03-17 at 14:05 +0000, Shukla, Pranjal wrote:
> From the configuration we have, does it mean that the primary will retain 32 WAL's
> of 1 GB each and then start evicting the first WAL as soon as the last one gets filled?
> In layman's term, 32GB is huge amount of data and I don't think that much changes
> during upgrades. In fact the total size of our database is 56 GB. Is my understanding
> correct?
>
> wal_keep_segments = 32
No, it means that the last 32 WAL segments of size 16MB are retained,
that is 0.5 GB.
"max_wal_size" is not the size of a WAL segment.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shukla, Pranjal | 2022-03-17 15:21:49 | Re: Query on WAL Optimization and Streaming Replication |
| Previous Message | Shukla, Pranjal | 2022-03-17 14:05:07 | Re: Query on WAL Optimization and Streaming Replication |