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.
Greetings,
Andres Freund
