The relationship between 'min_wal_size', 'max_wal_size' and 'wal_segment_size' is not record.

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/bug-reporting.html Description: configuration option 'min_wal_size' and 'max_wal_size' must be at least twice 'wal_segment_size', but none of these information was mentioned

Re: max_wal_size

a(e). > > > At the end of the work, CP makes a WAL record(plus symbol on WAL line). > > > > > > Back to the max_wal_size description: > > > "Maximum size to let the WAL grow to between automatic WAL checkpoints." > > > > > > As I understand now,

Re: max_wal_size

b e b e b e Checkpointer process for point A starts at a(b) and ends at a(e). At the end of the work, CP makes a WAL record(plus symbol on WAL line). Back to the max_wal_size description: "Maximum size to let the WAL grow to between automatic WAL checkpoints." As I u

Re: max_wal_size

e b e > > Checkpointer process for point A starts at a(b) and ends at a(e). > At the end of the work, CP makes a WAL record(plus symbol on WAL line). > > Back to the max_wal_size description: > "Maximum size to let the WAL grow to between automatic WAL checkpoints." >

Re: max_wal_size

David, I don't know whether a change along those lines to the configuration reference page is useful or not - I wouldn't make one without a comprehensive re-read of the actual background/learning section of the documentation. My gut instinct is that I just don't think the documentation can do

Re: max_wal_size

On Thu, May 28, 2020 at 2:21 AM wrote: > > Now we have the glossary. According to the glossary, a checkpoint has two > meanings. > > The first meaning is that this is a point: > "A point in the WAL sequence at which it is guaranteed that the heap and > index data files have been updated with all

Re: max_wal_size

starts at a(b) and ends at a(e). At the end of the work, CP makes a WAL record(plus symbol on WAL line). Back to the max_wal_size description: "Maximum size to let the WAL grow to between automatic WAL checkpoints." As I understand now, this is true when we talk about the checkp

Re: max_wal_size

On Wed, May 27, 2020, 14:12 wrote: > David, > > > For 0.5 you get 2/3rds consumption: ( n / ( 1 + 0.5 ) ) = n * 2/3 > > Exactly, for checkpoint_completion_target=0.5 the distance between > checkpoints is 2/3 of max_wal_size. > > But back to the documentation of ma

Re: max_wal_size

David, For 0.5 you get 2/3rds consumption: ( n / ( 1 + 0.5 ) ) = n * 2/3 Exactly, for checkpoint_completion_target=0.5 the distance between checkpoints is 2/3 of max_wal_size. But back to the documentation of max_wal_size. "Maximum size to let the WAL grow to between automati

Re: max_wal_size

k. > But the question is a little different. > > Suppose we have: version >= 11, no replication slots, archive_mode = > off. > Checkpoint_timeout is big enough, so checkpoints triggered only by > max_wal_size (1GB). > checkpoint_completion_target = 1. > > What size of

Re: max_wal_size

ots, archive_mode = off. Checkpoint_timeout is big enough, so checkpoints triggered only by max_wal_size (1GB). checkpoint_completion_target = 1. What size of WAL files will be generated between checkpoints? 1GB or 0.5GB? As I understand the description of max_wal_size(Maximum size to let the

Re: max_wal_size

On Wed, May 27, 2020 at 8:18 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/runtime-config-wal.html > Description: > > About parameter max_wal_size the documentation says

max_wal_size

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/runtime-config-wal.html Description: About parameter max_wal_size the documentation says that "Maximum size to let the WAL grow to between automatic WAL checkpoints." Is

Re: max_wal_size

On 27.05.2020 13:16, Andreas Kretschmer wrote: Am 27.05.20 um 12:11 schrieb Pavel Luzanov: Hello, About parameter max_wal_size the documentation <https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-MAX-WAL-SIZE> says: "Maximum size to let the WAL grow to betwee

Re: max_wal_size

Andreas, size between checkpoints, size of all wal's can be higher, see wal_keep_segments. Hm, I also thought, but after looking at the source , it seems like this is a restriction on all files

Re: max_wal_size

Am 27.05.20 um 12:11 schrieb Pavel Luzanov: Hello, About parameter max_wal_size the documentation <https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-MAX-WAL-SIZE> says: "Maximum size to let the WAL grow to between automatic WAL checkpoints." Is it co

max_wal_size

Hello, About parameter max_wal_size the documentation <https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-MAX-WAL-SIZE> says: "Maximum size to let the WAL grow to between automatic WAL checkpoints." Is it correct? The size between automatic WAL checkpo