Re: [HACKERS] patch: optimize information_schema.constraint_column_usage

2017-02-17 Thread Peter Eisentraut
On 2/2/17 08:27, Alexey Bashtanov wrote: > The view information_schema.constraint_column_usage becomes slow when > the number of columns and constraints raise to substantial values. > This is because of a join condition that allows only join filter to > enforce. The patch is to optimize it.

Re: [HACKERS] patch: optimize information_schema.constraint_column_usage

2017-02-03 Thread Ashutosh Bapat
Please add this patch to the commitfest so that it's not forgotten. On Fri, Feb 3, 2017 at 6:10 PM, Ashutosh Bapat wrote: > The patch applies cleanly. No regression test fails. > > On Thu, Feb 2, 2017 at 6:57 PM, Alexey Bashtanov wrote: >>

Re: [HACKERS] patch: optimize information_schema.constraint_column_usage

2017-02-03 Thread Ashutosh Bapat
The patch applies cleanly. No regression test fails. On Thu, Feb 2, 2017 at 6:57 PM, Alexey Bashtanov wrote: > Hello hackers, > > The view information_schema.constraint_column_usage becomes slow when the > number of columns and constraints raise to substantial values. > This

[HACKERS] patch: optimize information_schema.constraint_column_usage

2017-02-02 Thread Alexey Bashtanov
Hello hackers, The view information_schema.constraint_column_usage becomes slow when the number of columns and constraints raise to substantial values. This is because of a join condition that allows only join filter to enforce. The patch is to optimize it. See many_constraints.sql file