On 19 Sep 2014 19:40, Josh Berkus j...@agliodbs.com wrote:
On 09/19/2014 10:15 AM, Merlin Moncure wrote:
On Wed, Sep 17, 2014 at 7:11 PM, Josh Berkus j...@agliodbs.com wrote:
This is the core issue with abort-early plans; they depend on our
statistics being extremely accurate, which we
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
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
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,
On Sat, Sep 20, 2014 at 3:38 AM, Greg Stark st...@mit.edu 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 )
- b is
Greg Stark st...@mit.edu writes:
On 19 Sep 2014 19:40, Josh Berkus j...@agliodbs.com 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
On 09/19/2014 11:38 PM, Greg Stark wrote:
On 19 Sep 2014 19:40, Josh Berkus j...@agliodbs.com
mailto:j...@agliodbs.com wrote:
On 09/19/2014 10:15 AM, Merlin Moncure wrote:
On Wed, Sep 17, 2014 at 7:11 PM, Josh Berkus j...@agliodbs.com
mailto:j...@agliodbs.com wrote:
This is the core
