Postgres Pro
Downloads
Home   >   mailing lists

Re: Some clean-up work in get_cheapest_group_keys_order() - Mailing list pgsql-hackers

From David Rowley
Subject Re: Some clean-up work in get_cheapest_group_keys_order()
Date
Msg-id CAApHDvp=EzA3PAJ+wppB3U5JHn6UEkWQXuGHSJekS_bJer9p=w@mail.gmail.com
Whole thread Raw
In response to Re: Some clean-up work in get_cheapest_group_keys_order()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Wed, 13 Jul 2022 at 13:12, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> David Rowley <dgrowleyml@gmail.com> writes:
> > On Wed, 13 Jul 2022 at 11:02, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> Agreed, but I think there are other instances of that idiom that
> >> should be cleaned up while you're at it.
>
> > Agreed.  I imagine we should just do the remaining cleanup in master
> > only. Do you agree?
>
> No objection.

I've now pushed the original patch to 15 and master and also pushed a
cleanup commit to remove the list_truncate(list_copy instances from
master only.

Thanks for looking.

David

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)
Next
From: Amit Langote
Date:
Subject: Re: enable/disable broken for statement triggers on partitioned tables