Re: Performance degradation in commit 6150a1b0 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Performance degradation in commit 6150a1b0
Date
Msg-id CA+TgmobDYiX3fRxOxS-JOF_SFAQjA_8zrbcQGZdxPHBoMa4J8g@mail.gmail.com
Whole thread Raw
In response to Re: Performance degradation in commit 6150a1b0  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Fri, Feb 26, 2016 at 8:41 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Don't understand this. If a problem is caused by one of two things, first
> you check one, then the other.

I don't quite understand how you think that patch can be decomposed
into multiple, independent changes.  It was one commit because every
change in there is interdependent with every other one, at least as
far as I can see.  I don't really understand how you'd split it up, or
what useful information you'd hope to gain from testing a split patch.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Roma Sokolov
Date:
Subject: [PATCH] fix DROP OPERATOR to reset links to itself on commutator and negator
Next
From: Alvaro Herrera
Date:
Subject: Re: [REVIEW] In-core regression tests for replication, cascading, archiving, PITR, etc.