Re: [HACKERS] Performance problem partially identified

Hannu Krosing wrote:
> 
> Tom Lane wrote:
> >
> > It looks to me like something is broken such that bufmgr.c *always*
> > thinks that a buffer is dirty (and needs written out) when it is
> > released.
> 
> That could also explain why the performance increases quite noticeably
> even for _select_ queries when you specify "no fsync" for backend.
> (I have'nt checked it lately, but it was the case about a year ago)

Enev selects try to update t_infomask to avoid pg_log lookup
for other queries.

Vadim