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-12-01T06:29:32Z
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 Wed, Nov 30, 2011 at 1:37 AM, YAMAMOTO Takashi
> <yamt@mwd.biglobe.ne.jp> wrote:
>>> 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.
> 
> Oh, that's interesting.  Why do you want to avoid frequent fsyncs?

simply because it was expensive on my environment.

> I
> thought the point of synchronous_commit=off was to move the fsyncs to
> the background, but not necessarily to decrease the frequency.

it makes sense.
but it's normal for users to abuse features. :)

YAMAMOTO Takashi

> 
> -- 
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
> 
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers