From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | Torsten Krah <krah(dot)tm(at)gmail(dot)com> |
Cc: | "pgsql-general\(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Force WAL cleanup on running instance |
Date: | 2020-03-11 16:46:33 |
Message-ID: | 87sgievnyu.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Torsten Krah <krah(dot)tm(at)gmail(dot)com> writes:
> Am Mittwoch, den 11.03.2020, 15:45 +0000 schrieb Simon Riggs:
>
>> The size of the task varies, so sometimes takes longer than 60s,
>> depending
>> upon your hardware.
>
> Yes that's what I am observing and why I am asking if there is some
> select statement or command which triggers that task and returns after
> it has finished - as I can't predict how long that task may run.
If your site can afford a restart after the bulk load,
1. Clean shutdown.
2. pg_resetwal
3. Start
That should leave you with a very small N WAL files, perhaps just 1,
though I've not run it lately to reverify.
HTH
>
> kind regards
>
> Torsten
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Förster | 2020-03-11 17:29:23 | Re: Force WAL cleanup on running instance |
Previous Message | Torsten Krah | 2020-03-11 16:01:54 | Re: Force WAL cleanup on running instance |