Re: [HACKERS] Performance problem partially identified

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Hannu Krosing <hannu(at)trust(dot)ee>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Performance problem partially identified
Date: 1999-05-29 04:58:23
Message-ID: 374F73EF.B47F4013@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim Mikheev 1999-05-29 05:10:16 Re: [HACKERS] Re: Performance problem partially identified
Previous Message Vadim Mikheev 1999-05-29 04:55:28 Re: [HACKERS] Performance problem partially identified