Re: [HACKERS] Cached plans and statement generalization - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Cached plans and statement generalization
Date
Msg-id 22696.1494527462@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Cached plans and statement generalization  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [HACKERS] Cached plans and statement generalization  (Andres Freund <andres@anarazel.de>)
Re: [HACKERS] Cached plans and statement generalization  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Good point.  I think we need to do some measurements to see if the
> parser-only stage is actually significant.  I have a hunch that
> commercial databases have much heavier parsers than we do.

FWIW, gram.y does show up as significant in many of the profiles I take.
I speculate that this is not so much that it eats many CPU cycles, as that
the constant tables are so large as to incur lots of cache misses.  scan.l
is not quite as big a deal for some reason, even though it's also large.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Euler Taveira
Date:
Subject: Re: [HACKERS] Logical decoding truncate
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Cached plans and statement generalization