Re: WAL CPU overhead/optimization (was Master-slave visibility order) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: WAL CPU overhead/optimization (was Master-slave visibility order)
Date
Msg-id CA+TgmobO+KXYXbuRQb7G1ktZoxtSTfDo-yBNdN2Duq4ZvSYZZQ@mail.gmail.com
Whole thread Raw
In response to Re: WAL CPU overhead/optimization (was Master-slave visibility order)  (Ants Aasma <ants@cybertec.at>)
Responses Re: WAL CPU overhead/optimization (was Master-slave visibility order)
List pgsql-hackers
On Thu, Aug 29, 2013 at 8:22 PM, Ants Aasma <ants@cybertec.at> wrote:
> I might give it a shot later this cycle as I have familiarized my self
> with the problem domain anyway. I understand the appeal of staying
> with what we have, but this would cap the speedup at 4x and has large
> caveats with the extra lookup tables. A 28x speedup might be worth the
> extra effort.

I agree.  However, on the flip side, a bird in the hand is worth two
in the bush.  A patch that just does the same thing faster is likely
to be less controversial than changing the algorithm, and does not
preclude changing the algorithm later.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [9.3 doc fix] clarification of Solaris versions
Next
From: Robert Haas
Date:
Subject: Re: logical changeset generation v5