Re: Refactoring the checkpointer's fsync request queue

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, sdn(at)amazon(dot)com
Subject: Re: Refactoring the checkpointer's fsync request queue
Date: 2018-12-01 12:47:27
Message-ID: CA+q6zcV=p=1G2Z8itJ9=tAn=b8ha3pO4RQCMt9YXOEutRV33YQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Mon, Nov 26, 2018 at 11:47 PM Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
>
> On Fri, Nov 23, 2018 at 5:45 PM Thomas Munro
> <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> > I do have a new plan though...
>
> Ugh. The plan in my previous email doesn't work, I was confused about
> the timing of the buffer header update. Back to the drawing board.

Any chance to share the drawing board with the ideas? :)

On the serious note, I assume you have plans to work on this during the next
CF, right?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2018-12-01 12:59:50 Re: Protect syscache from bloating with negative cache entries
Previous Message Dmitry Dolgov 2018-12-01 12:41:48 Re: Make foo=null a warning by default.