| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | "Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com> |
| Cc: | Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Estimating wal_keep_size |
| Date: | 2021-06-18 18:27:44 |
| Message-ID: | CAOBaU_a-BanEBN=5cP8UP92Cw7Yst-okmHYi9o1hYU9ZfuASHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Le sam. 19 juin 2021 à 02:13, Dean Gibson (DB Administrator) <
postgresql(at)mailpen(dot)com> a écrit :
>
> Granted, but the same question arises about the value for
> max_slot_wal_keep_size. Setting either too low risks data loss, & setting
> either too high results in unnecessary disk space used. The question was,
> is the estimated VALUE reasonable under the circumstances?
>
it may be, until one day it won't be. and that day usually happens. when
you set up this kind of limit you choose service availability over your
data, so you have to accept that it may not be enough. if this is a problem
don't setup a limit.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vijaykumar Jain | 2021-06-18 18:40:08 | Re: Estimating wal_keep_size |
| Previous Message | Dean Gibson (DB Administrator) | 2021-06-18 18:13:14 | Re: Estimating wal_keep_size |