| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, hlinnaka <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: [HACKERS] WAL logging problem in 9.4.3? |
| Date: | 2019-11-24 12:53:16 |
| Message-ID: | 20191124125316.GC2266@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 23, 2019 at 11:35:09AM -0500, Noah Misch wrote:
> That longstanding optimization is too useful to remove, but likely not useful
> enough to add today if we didn't already have it. The initial-data-load use
> case remains plausible. I can also imagine using wal_level=minimal for data
> warehouse applications where one can quickly rebuild from the authoritative
> data.
I can easily imagine cases where a user would like to use the benefit
of the optimization for an initial data load, and afterwards update
wal_level to replica so as they avoid the initial WAL burst which
serves no real purpose. So the first argument is pretty strong IMO,
the second much less.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2019-11-24 13:00:10 | [PATCH] Fix var declaration according scanf specification, |
| Previous Message | Michael Paquier | 2019-11-24 12:48:05 | Re: Copyright information in source files |