Horton

Re: synchronous commit vs. hint bits

YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>

View thread
From: yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi)
To: robertmhaas@gmail.com
Cc: simon@2ndquadrant.com, pgsql-hackers@postgresql.org
Date: 2011-11-30T06:37:29Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Allow hint bits to be set sooner for temporary and unlogged tables.

hi,

> On Tue, Nov 29, 2011 at 1:42 AM, YAMAMOTO Takashi
> <yamt@mwd.biglobe.ne.jp> wrote:
>>> On Mon, Nov 7, 2011 at 5:26 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>>>
>>>>> 5. Make the WAL writer more responsive, maybe using latches, so that
>>>>> it doesn't take as long for the commit record to make it out to disk.
>>>>
>>>> I'm working on this already as part of the update for power
>>>> reduction/group commit/replication performance.
>>>
>>> I extracted this from my current patch for you to test.
>>
>> is it expected to produce more frequent fsync?
> 
> Yes, I would expect that.  What kind of increase are you seeing?  Is
> it causing a problem for you, or are you just making an observation?

i was curious because my application uses async commits mainly to
avoid frequent fsync.  i have no numbers right now.

YAMAMOTO Takashi

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