Re: C trigger significantly slower than PL/pgSQL? - Mailing list pgsql-interfaces

From Tom Lane
Subject Re: C trigger significantly slower than PL/pgSQL?
Date
Msg-id 1342580.1681400531@sss.pgh.pa.us
Whole thread Raw
In response to Re: C trigger significantly slower than PL/pgSQL?  (pgchem pgchem <pgchem@tuschehund.de>)
Responses Re: C trigger significantly slower than PL/pgSQL?  (Ernst-Georg Schmid <pgchem@tuschehund.de>)
List pgsql-interfaces
pgchem pgchem <pgchem@tuschehund.de> writes:
> as requested, here is the C code:
> ...
> ret = SPI_execute("SELECT pg_backend_pid() = ANY((SELECT pid FROM pg_stat_activity WHERE backend_type = 'logical
replicationworker'))::boolean AS is_replicated", true, 1); 

Yeah, there's your problem.  Each time through the trigger, that query
is being parsed, planned, and executed from scratch.  plpgsql knows
how to cache the planned statement, so it's doing less work per-call.

            regards, tom lane



pgsql-interfaces by date:

Previous
From: pgchem pgchem
Date:
Subject: Re: C trigger significantly slower than PL/pgSQL?
Next
From: Ernst-Georg Schmid
Date:
Subject: Re: C trigger significantly slower than PL/pgSQL?