| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, craig(at)2ndquadrant(dot)com |
| Subject: | Re: CF bug fix items |
| Date: | 2018-06-11 18:31:11 |
| Message-ID: | 9d38cece-9148-001d-d3bc-68d968f87565@2ndQuadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-06-11 18:33:27 | Re: automating perl compile time checking |
| Previous Message | Jeff Davis | 2018-06-11 18:13:45 | Re: Spilling hashed SetOps and aggregates to disk |