Re: suggest to rename enable_incrementalsort - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: suggest to rename enable_incrementalsort
Date
Msg-id 836dfad2-d15b-36f1-9121-142bd505e090@2ndquadrant.com
Whole thread Raw
In response to Re: suggest to rename enable_incrementalsort  (James Coleman <jtc331@gmail.com>)
List pgsql-hackers
On 2020-07-02 17:25, James Coleman wrote:
> I think the change makes a lot of sense. The only reason I had it as
> enable_incrementalsort in the first place was trying to broadly
> following the existing GUC names, but as has already been pointed out,
> there's a lot of variation there, and my version of the patch already
> changed it to be more readable (at one point it was
> enable_incsort...which is short...but does not have an obvious
> meaning).
> 
> I've attached a patch to make the change,

committed

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Mitar
Date:
Subject: Re: Persist MVCC forever - retain history
Next
From: Dilip Kumar
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions