Re: pgsql: Fix FK checks of TRUNCATE involving partitioned tables

2018-07-14 Thread Michael Paquier
On Thu, Jul 12, 2018 at 04:26:17PM +, Alvaro Herrera wrote: > Fix FK checks of TRUNCATE involving partitioned tables > > Author: Álvaro Herrera > Reviewed-by: Michael Paquiër > Discussion: https://postgr.es/m/[email protected] Just a note, using 'ë' in the first

pgsql: Fix hashjoin costing mistake introduced with inner_unique optimi

2018-07-14 Thread Tom Lane
Fix hashjoin costing mistake introduced with inner_unique optimization. In final_cost_hashjoin(), commit 9c7f5229a allowed inner_unique cases to follow a code path previously used only for SEMI/ANTI joins; but it neglected to fix an if-test within that path that assumed SEMI and ANTI were the only

pgsql: Fix hashjoin costing mistake introduced with inner_unique optimi

2018-07-14 Thread Tom Lane
Fix hashjoin costing mistake introduced with inner_unique optimization. In final_cost_hashjoin(), commit 9c7f5229a allowed inner_unique cases to follow a code path previously used only for SEMI/ANTI joins; but it neglected to fix an if-test within that path that assumed SEMI and ANTI were the only

pgsql: Fix hashjoin costing mistake introduced with inner_unique optimi

2018-07-14 Thread Tom Lane
Fix hashjoin costing mistake introduced with inner_unique optimization. In final_cost_hashjoin(), commit 9c7f5229a allowed inner_unique cases to follow a code path previously used only for SEMI/ANTI joins; but it neglected to fix an if-test within that path that assumed SEMI and ANTI were the only

Re: pgsql: Fix FK checks of TRUNCATE involving partitioned tables

2018-07-14 Thread Alvaro Herrera
On 2018-Jul-14, Michael Paquier wrote: > On Thu, Jul 12, 2018 at 04:26:17PM +, Alvaro Herrera wrote: > > Fix FK checks of TRUNCATE involving partitioned tables > > > > Author: Álvaro Herrera > > Reviewed-by: Michael Paquiër > > Discussion: > > https://postgr.es/m/20180711000624.zmeizicibxe