Re: track_planning causing performance regression

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, "Tharakan, Robins" <tharar(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: track_planning causing performance regression
Date: 2020-07-03 02:48:58
Message-ID: 9f95766f-52d1-c0ec-cf31-b091028bafb5@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020/07/03 11:43, Peter Geoghegan wrote:
> On Thu, Jul 2, 2020 at 7:39 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>> So I pushed the patch and changed default of track_planning to off.
>
> I have closed out the open item I created for this.

Thanks!!

I added the patch that replaces spinlock with lwlock in pgss, into CF-2020-09.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2020-07-03 02:51:51 Re: Persist MVCC forever - retain history
Previous Message Justin Pryzby 2020-07-03 02:46:49 Re: Default setting for enable_hashagg_disk (hash_mem)