Re: corrupt pages detected by enabling checksums - Mailing list pgsql-hackers

From Robert Haas
Subject Re: corrupt pages detected by enabling checksums
Date
Msg-id CA+TgmoYm4iQBaDTPjVDd2C=CNOcHZBcQdxTTf=Ss1GZS0ed5_Q@mail.gmail.com
Whole thread Raw
In response to Re: corrupt pages detected by enabling checksums  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: corrupt pages detected by enabling checksums
List pgsql-hackers
On Sat, Apr 6, 2013 at 10:44 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> I feel pretty strongly that we shouldn't add any such complications to
> XLogInsert() itself, its complicated enough already and it should be
> made simpler, not more complicated.

+1, emphatically.  XLogInsert is a really nasty scalability
bottleneck.  We need to move as much logic out of that function as
possible, and particularly out from under WALInsertLock.

...Robert



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GSOC] questions about idea "rewrite pg_dump as library"
Next
From: Alvaro Herrera
Date:
Subject: Re: [sepgsql 3/3] Add db_procedure:execute permission checks