Re: Costing elided SubqueryScans more nearly correctly
От
Alvaro Herrera
Тема
Re: Costing elided SubqueryScans more nearly correctly
Дата
Msg-id
20220718163619.g4xrd63x6yvlpjzf@alvherre.pgsql
Ответ на
Re: Costing elided SubqueryScans more nearly correctly (Richard Guo)
Список
Дерево обсуждения
Costing elided SubqueryScans more nearly correctly Tom Lane <tgl@sss.pgh.pa.us>
Re: Costing elided SubqueryScans more nearly correctly Tom Lane <tgl@sss.pgh.pa.us>
Re: Costing elided SubqueryScans more nearly correctly Richard Guo <guofenglinux@gmail.com>
Re: Costing elided SubqueryScans more nearly correctly Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: Costing elided SubqueryScans more nearly correctly Tom Lane <tgl@sss.pgh.pa.us>
Re: Costing elided SubqueryScans more nearly correctly Richard Guo <guofenglinux@gmail.com>
Re: Costing elided SubqueryScans more nearly correctly Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: Costing elided SubqueryScans more nearly correctly Tom Lane <tgl@sss.pgh.pa.us>
Re: Costing elided SubqueryScans more nearly correctly Tom Lane <tgl@sss.pgh.pa.us>
Re: Costing elided SubqueryScans more nearly correctly Richard Guo <guofenglinux@gmail.com>
Re: Costing elided SubqueryScans more nearly correctly Etsuro Fujita <etsuro.fujita@gmail.com>
On 2022-Jul-18, Richard Guo wrote: > BTW, not related to this patch, the new lines for parallel_aware check > in setrefs.c are very wide. How about wrap them to keep consistent with > arounding codes? Not untrue! Something like this, you mean? Fixed the nearby typo while at it. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
В списке pgsql-hackers по дате отправления
