| From: | SASIKUMAR Devaraj <sashikumard(at)yahoo(dot)com> |
|---|---|
| To: | laurenz(dot)albe(at)cybertec(dot)at, Bryon Roché <kain(at)kain(dot)org>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to speed WAL apply in destination |
| Date: | 2022-12-09 10:57:03 |
| Message-ID: | 203270855.2602687.1670583423055@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
During certain interval there is huge WAL file generation f3om primary around 300gb/hr which delays sync in secondary by atleast 30 mins. Other time it is normal
Sent from Yahoo Mail on Android
On Fri, Dec 9, 2022 at 4:20 PM, Laurenz Albe<laurenz(dot)albe(at)cybertec(dot)at> wrote: On Fri, 2022-12-09 at 08:47 +0000, Bryon Roché wrote:
> On December 9, 2022 5:02:59 AM UTC, SASIKUMAR Devaraj <sashikumard(at)yahoo(dot)com> wrote:
> > How to speed up WAL apply process in secondary? Any parameter available from postgres, apart from disk speed?
>
> There are fsync parameters which can be set to off that may provide a modest speed increase, at the cost of removing crash safety.
That is spectacularly bad advice.
Is the disk the bottleneck at all?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2022-12-09 14:21:39 | Re: How to speed WAL apply in destination |
| Previous Message | Laurenz Albe | 2022-12-09 10:50:07 | Re: How to speed WAL apply in destination |