From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Andrey Zhidenkov <pensnarik(at)gmail(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Notes about Pl/PgSQL assignment performance |
Date: | 2017-12-19 14:08:26 |
Message-ID: | 20171219140826.bhpwyyy3alyvlice@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrey Zhidenkov wrote:
> I've digged into the source code a little bit and found that chain:
>
> PLPGSQL_STMT_ASSIGN -> exec_stmt_assign() -> exec_assign_expr()
> -> exec_eval_expr() -> exec_run_select()
> -> SPI_execute_plan_with_paramlist() -> _SPI_execute_plan() which finnaly
> calls PushActiveSnapshot() and PopActiveSnapshot() wich just do memory
> context allocations and use malloc() to copy snaphot.
>
> Maybe I have missed something?
Yes.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2017-12-19 14:11:11 | Re: WIP Patch: Pgbench Serialization and deadlock errors |
Previous Message | Marina Polyakova | 2017-12-19 14:07:47 | Re: WIP Patch: Pgbench Serialization and deadlock errors |