From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Michael(dot)Meskes(at)usa(dot)net, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] performance test |
Date: | 1999-01-19 06:13:14 |
Message-ID: | 36A4227A.BD961413@krs.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> > You've seen disadvantages of our unperfect buffer manager -:)
> > When server need in buffer for new data comming and there is
> > no unused buffers in pool (i.e. - all buffers filled with new
> > data and marked as dirty), server gets some dirty buffer,
> > writes it AND FSYNC file. So, server does many fsyncs
> > even with BEGIN/END while should do _one_ fsync at COMMIT.
> >
> > Having this problem fixed you wouldn't had so big difference
> > between -F and BEGIN/END-no-F.
>
> Is this idea still reasonable?
>
> ---------------------------------------------------------------------------
>
> Here is an archive of the pg_log discussion.
Thanks for archive, Bruce.
But delayed fsync is another idea.
bufmgr has to be fixed anyway.
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Samersoff | 1999-01-19 08:11:22 | Good Idea ;-)) |
Previous Message | Bruce Momjian | 1999-01-19 06:03:16 | Re: [HACKERS] Postgres Speed or lack thereof |