Re: query very slow when enable_seqscan=on - Mailing list pgsql-bugs

From Tom Lane
Subject Re: query very slow when enable_seqscan=on
Date
Msg-id 25494.1152036954@sss.pgh.pa.us
Whole thread Raw
In response to Re: query very slow when enable_seqscan=on  (Tomasz Ostrowski <tometzky@batory.org.pl>)
Responses Re: query very slow when enable_seqscan=on  (Tomasz Ostrowski <tometzky@batory.org.pl>)
List pgsql-bugs
Tomasz Ostrowski <tometzky@batory.org.pl> writes:
> So why estimate regex expressions if there is no estimation possible?
> Let's set this estimate to be pessimistic (match everything or
> everything not null) and it will choose better plans.

Better plans for this specific example, worse plans for other cases.
Life is not that simple.

            regards, tom lane

pgsql-bugs by date:

Previous
From: tomas@tuxteam.de
Date:
Subject: Re: query very slow when enable_seqscan=on
Next
From: "Phil Frost"
Date:
Subject: BUG #2512: pg_dump produces unrestorable output when table and serial sequence are not in the same schema