Search Postgresql Archives

Re: Planner: rows=1 after "similar to" where condition.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Joris Dobbelsteen" <Joris@xxxxxxxxxxxxxxxxxxxxx> writes:
> "Bitmap Heap Scan on log_syslog syslog  (cost=11168.32..16988.84 rows=1
> width=221) (actual time=11145.729..30067.606 rows=212 loops=1)"
> "  Recheck Cond: (((program)::text = 'amavis'::text) AND
> ((facility)::text = 'mail'::text))"
> "  Filter: (((priority)::text = 'notice'::text) AND ((text)::text ~
> '***:^(?:amavis\\[[0-9]+\\]: \\([0-9]+-[-0-9]+\\) Passed [A-Za-z0-9]+,
> [][0-9\\.]* <[^<>]+> -> <[^<>]+>, Message-ID: <[^<>]+>,
> (Resent-Message-ID: <[^<>]+>, |)mail.id: [^ ,]+, Hits: [-+0-9\\.,]+,
> queued.as: [^ ,]+, [0-9]+ ms)$'::text))"

It's not too surprising that you'd get a small selectivity estimate
for such a long regexp; the default estimate is just based on the amount
of fixed text in the pattern, and you've got a lot.

If you increase the stats target for the column to 100 or more then it
will try actually applying the regexp to all the histogram entries.
That might or might not give you a better estimate.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
       message can get through to the mailing list cleanly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux