Re: Re: [HACKERS] GSoC 2015 proposal: Improve the performance of “ALTER TABLE .. SET LOGGED / UNLOGGED” statement - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Re: [HACKERS] GSoC 2015 proposal: Improve the performance of “ALTER TABLE .. SET LOGGED / UNLOGGED” statement
Date
Msg-id 20150709135621.GZ10242@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] Re: [HACKERS] GSoC 2015 proposal: Improve the performance of “ALTER TABLE .. SET LOGGED / UNLOGGED” statement  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Responses Re: [HACKERS] Re: [HACKERS] GSoC 2015 proposal: Improve the performance of “ALTER TABLE .. SET LOGGED / UNLOGGED” statement
Re: Re: [HACKERS] GSoC 2015 proposal: Improve the performance of “ALTER TABLE .. SET LOGGED / UNLOGGED” statement
List pgsql-hackers
On 2015-07-09 10:39:35 -0300, Fabrízio de Royes Mello wrote:
> If the "wal_level=minimal" we don't need to force the wal log of the
> contents. If the "wal_level != minimal" we need just to xlog all the pages,
> but in both cases we don't need the extra job to create a new datafiles and
> copy the contents between them. So we'll improve performance, or am I
> missing something?

Sure. It'll be a bit faster. I just don't see the peformance increase in
not that common situations being worth the price we'll pay in
development, code review, debugging and then maintaining some nontrivial
code. If this were likely to be a 15 line patch, I'd think differently.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Supporting TAP tests with MSVC and Windows
Next
From: Michael Paquier
Date:
Subject: Re: Set of patch to address several Coverity issues