| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Sean Chittenden <seanc(at)joyent(dot)com> |
| Subject: | Re: WAL prefetch |
| Date: | 2018-06-16 19:23:03 |
| Message-ID: | 20180616192303.2hpxldoqbwbgzgys@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-06-13 16:09:45 +0300, Konstantin Knizhnik wrote:
> Usage:
> 1. At master: create extension wal_prefetch
> 2. At replica: Call pg_wal_prefetch() function: it will not return until you
> interrupt it.
FWIW, I think the proper design would rather be a background worker that
does this work. Forcing the user to somehow coordinate starting a
permanently running script whenever the database restarts isn't
great. There's also some issues around snapshots preventing vacuum
(which could be solved, but not nicely).
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2018-06-16 19:34:30 | Re: WAL prefetch |
| Previous Message | Andres Freund | 2018-06-16 19:02:10 | Re: WAL prefetch |