From: | "Shukla, Pranjal" <pshukla(at)akamai(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
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 15:21:49 |
Message-ID: | 23657103-775B-415A-BEC2-B00B7B5B8D86@akamai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ok,
Then what will increase the size of the WAL?
Sent from my iPhone
> On 17-Mar-2022, at 8:08 PM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> 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://urldefense.com/v3/__https://www.cybertec-postgresql.com__;!!GjvTz_vk!CfWoaVi0_A_FauqITD6xevYV9YuIJGyWWueduHyTOiD3CY65CJorQpYhD5zbUA$
From | Date | Subject | |
---|---|---|---|
Next Message | Japin Li | 2022-03-17 15:56:01 | Re: Support logical replication of DDLs |
Previous Message | Laurenz Albe | 2022-03-17 14:38:31 | Re: Query on WAL Optimization and Streaming Replication |