Re: Avoiding adjacent checkpoint records - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Avoiding adjacent checkpoint records
Date
Msg-id CA+TgmobwWz3tQRth=EB=vcbLxtWz+b8aJ=MckdEE_kKeS33ZTA@mail.gmail.com
Whole thread Raw
In response to Re: Avoiding adjacent checkpoint records  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Avoiding adjacent checkpoint records  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jun 6, 2012 at 4:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I felt (and still feel) that this was misguided.
>
> Looking at it again, I'm inclined to agree.  The behavior was entirely
> correct up until somebody decided to emit a continuing stream of
> XLOG_RUNNING_XACTS WAL records even when the system is idle.  Why did
> we not fix it by fixing that?

That's exactly what I think we should have done.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Avoiding adjacent checkpoint records
Next
From: Tom Lane
Date:
Subject: Re: creating objects in pg_catalog