Horton

Re: Improve behavior of concurrent TRUNCATE

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: "Bossart, Nathan" <bossartn@amazon.com>
Cc: Postgres hackers <pgsql-hackers@postgresql.org>
Date: 2018-08-10T16:30:21Z
Lists: pgsql-hackers 
On Thu, Aug 09, 2018 at 05:55:54PM +0000, Bossart, Nathan wrote:
> On 8/9/18, 11:31 AM, "Michael Paquier" <michael@paquier.xyz> wrote:
>> Thanks, I have updated the patch as you suggested.  Any more
>> improvements to it that you can foresee?
> 
> Looks good to me.

Okay, pushed to HEAD.  Now remains the cases for VACUUM and we will be
good.  I still need to look more deeply at the last patch sent..
--
Michael

Commits

  1. Improve TRUNCATE by avoiding early lock queue