Re: corrupt pages detected by enabling checksums

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: corrupt pages detected by enabling checksums
Date: 2013-04-10 23:37:48
Message-ID: CA+TgmoYm4iQBaDTPjVDd2C=CNOcHZBcQdxTTf=Ss1GZS0ed5_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Apr 6, 2013 at 10:44 AM, Andres Freund <andres(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-04-10 23:49:50 Re: [sepgsql 3/3] Add db_procedure:execute permission checks
Previous Message Tom Lane 2013-04-10 22:17:57 Re: [GSOC] questions about idea "rewrite pg_dump as library"