| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org, Yi Sun <yinan81(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_wal directory max size |
| Date: | 2022-12-22 04:44:01 |
| Message-ID: | D3B925FC-564F-4972-836B-55601CF36982@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 22 December 2022 04:00:57 CET, Yi Sun <yinan81(at)gmail(dot)com> wrote:
>Hello guys,
>
>We are planning the server disk space, pg_wal directory max size is wal
>file size*wal_keep_segments? or is it also decided by other parameters
>please? We tried to search for this, but could not find the answer
>
>For example our postgresql is 9.6 below parameters value, is the pg_wal
>directory max size 320*16MB please? Thank you
>wal file size 16MB
>wal_keep_segments = 320
>min_wal_size = 1GB
>max_wal_size = 2GB
>
>Best Regards
>Dennis
No, you need space to store all wal's between 2 checkpoints. So it depends more on the checkpoint parameters and your workload. Plus wal_keep_segments...
9.6 is out of support.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2022-12-22 07:41:06 | Re: pg_wal directory max size |
| Previous Message | David Rowley | 2022-12-22 03:56:30 | Re: Implementing foreign data wrappers and avoiding n+1 querying |