Re: executor relation handling - Mailing list pgsql-hackers

From Tom Lane
Subject Re: executor relation handling
Date
Msg-id 28910.1539013124@sss.pgh.pa.us
Whole thread Raw
In response to Re: executor relation handling  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: executor relation handling  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Re: executor relation handling  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
I wrote:
> Keeping that comparison in mind, I'm inclined to think that 0001
> is the best thing to do for now.  The incremental win from 0002
> is not big enough to justify the API break it creates, while your
> 0005 is not really attacking the problem the right way.

I've pushed 0001 now.  I believe that closes out all the patches
discussed in this thread, so I've marked the CF entry committed.
Thanks for all the hard work!

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: exclude tmp_check and tmp_install from pgindent
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL 12, JIT defaults