Re: Slow system due to ReorderBufferGetTupleBuf?

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Martin Moore <martin(dot)moore(at)avbrief(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Slow system due to ReorderBufferGetTupleBuf?
Date: 2018-01-01 17:44:39
Message-ID: CAH2-Wzk6+3qCxFwbDZOH-iASzJMheKa32_XebhyLAwVyHg6kxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jan 1, 2018 at 8:56 AM, Martin Moore <martin(dot)moore(at)avbrief(dot)com> wrote:
> Can someone shed some light on this and advise how to prevent it reoccurring?

You're using v10, which has these two commits:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=58b25e98106dbe062cec0f3d31d64977bffaa4af

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=9fab40ad32efa4038d19eaed975bb4c1713ccbc0

Unfortunately, per the commit message of the first commit, it doesn't
look like the tuple allocator uses any new strategy, at least until
this v11 commit:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=a4ccc1cef5a04cc054af83bc4582a045d5232cb3

My guess is that that would make a noticeable difference, once v11
becomes available. Could you test this yourself by building from the
master branch?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2018-01-01 18:11:48 Re: Use of Port 5433 with Postgresql 9.6
Previous Message Graeme 2018-01-01 17:42:28 Use of Port 5433 with Postgresql 9.6