On 06/11/2018 01:11 PM, Andres Freund wrote:
On 2018-06-11 13:30:27 +0900, Michael Paquier wrote:
"Fix the optimization to skip WAL-logging on table created in same
transaction" has been in 10 (!) commitfests. It's seen no substantive action
since November. It has a bunch of authors and reviewers listed, Surely
somebody can move it forward?
I think that this is a complicated topic, which results in a rather
large and invasive patch introducing new logic concepts in order to fix
a rather narrow use-case. So I am wondering if it is really something
we ought to fix here..
I think we absolutely definitely need to fix it, or remove
wal_level=minimal. It's a failure to provide the fundamental guarantees
a database should provide. It seems not unreasonable to commit something
to v11 and then backpatch a bit later, to manage risk, however.
What goes into 11 doesn't have the same non-breakage requirements as
something on the back branches.
This bug report has been around far too long, and I suspect the main
reason we've not been bitten by it more is that most people don't run
with minimal.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
