Re: plan cache overhead on plpgsql expression - Mailing list pgsql-hackers

From Robert Haas
Subject Re: plan cache overhead on plpgsql expression
Date
Msg-id CA+TgmoaygQ-mop7m2RbKtZnjWFZB8K71+Szdu-tYmZuz7-joFw@mail.gmail.com
Whole thread Raw
In response to Re: plan cache overhead on plpgsql expression  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Mar 21, 2020 at 2:24 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> With this patch, perf shows the hotspots on Pavel's original example
> as being
>
> +   19.24%    19.17%         46470  postmaster       plpgsql.so                   [.] exec_eval_expr
> +   15.19%    15.15%         36720  postmaster       plpgsql.so                   [.] plpgsql_param_eval_var
> +   14.98%    14.94%         36213  postmaster       postgres                     [.] ExecInterpExpr
> +    6.32%     6.30%         15262  postmaster       plpgsql.so                   [.] exec_stmt
> +    6.08%     6.06%         14681  postmaster       plpgsql.so                   [.] exec_assign_value

That's pretty sweet. As you say, there's probably some way to
eliminate some of the non-plancache overhead, but it's still a big
improvement.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Berserk Autovacuum (let's save next Mandrill)
Next
From: Tom Lane
Date:
Subject: Re: Spurious "apparent wraparound" via SimpleLruTruncate() rounding