Re: [PERFORM] Yet another abort-early plan disaster on 9.3

On 09/19/2014 11:38 PM, Greg Stark wrote: > > On 19 Sep 2014 19:40, "Josh Berkus" > wrote: >> >> On 09/19/2014 10:15 AM, Merlin Moncure wrote: >> > On Wed, Sep 17, 2014 at 7:11 PM, Josh Berkus > wrote: >> >> This is the core issue with abort-ea

Re: [PERFORM] Yet another abort-early plan disaster on 9.3

Greg Stark writes: > On 19 Sep 2014 19:40, "Josh Berkus" wrote: >> Yeah, here's an example of the canonical case: >> >> Table t1 ( a, b, c ) >> >> - "b" is low-cardinality >> - "c" is high-cardinality >> - There are separate indexes on both b and c. >> >> SELECT a, b, c FROM t1 >> WHERE b = 2

Re: [PERFORM] Yet another abort-early plan disaster on 9.3

On Sat, Sep 20, 2014 at 3:38 AM, Greg Stark wrote: >> > Is there a canonical case of where 'abort early' plans help? (I'm new >> > to that term -- is it a recent planner innovation...got any handy >> > links?) >> >> Yeah, here's an example of the canonical case: >> >> Table t1 ( a, b, c ) >> >> -

Re: [PERFORM] query a table with lots of coulmns

Hi, ok here are my schemata : cachetable : 30 - 50 Mio rows, worktable 5 Mio - 25 Mio CREATE TABLE cachetable ( a text, b text NOT NULL, c text, d text, e timestamp without time zone DEFAULT now(), f text, s1 integer DEFAULT 0, s2 integer DEFAULT 0, s3 integer DEFAULT 0, s

Re: [PERFORM] query a table with lots of coulmns

>At first, thanks for your fast and comprehensive help. > >The structure of my cache table is > >a text , b text NOT NULL , c text , d text , e timestamp without >timezone DEFAULT now(), f text, s1 integer DEFAULT 0, s2 integer >DEFAULT 0, s3 integer DEFAULT 0, ... ,s512 DEFAULT 0 >additional co

Re: [PERFORM] query a table with lots of coulmns

At first, thanks for your fast and comprehensive help. The structure of my cache table is a text , b text NOT NULL , c text , d text , e timestamp without timezone DEFAULT now(), f text, s1 integer DEFAULT 0, s2 integer DEFAULT 0, s3 integer DEFAULT 0, ... ,s512 DEFAULT 0 additional constra