Hi,
I have run a test with pgbench against two cloud vendors (settings,
parameters almost the same).
Both Postgres (or whatever they do internally when they call it as
Postgres offering, NOT Aurora or so :-) )
I have got a strange result that cloud vendor 1 is performing almost
Today, the only feasible solution is not to create more than 64 subtransactions
(savepoints or PL/pgSQL EXCEPTION clauses) per transaction.
Don't use extensions or the JDBC driver option to simulate statement level
rollback, that is the road to hell.
You mean extensions to simulate a
Subject: Memory Growth Issue in "Backend" after Creating and Executing
Multiple "Named Prepared Statements" with Different Names and Executing
DISCARD ALL Finally.
Product: PostgreSQL 14
Dear Technical Support Team,
We reach out to you to report an issue related to memory growth in
PostgreSQL
On 01/02/2024 15:40, Daniel Blanch Bataller wrote:
We have attached a small C program with libpq that demonstrates this
issue, along with the program's output and the execution of the "ps aux"
program.
There is no DISCARD ALL command in the test program you included. I can
see the DISCARD
On Thu, 2024-02-01 at 11:50 +, James Pang (chaolpan) wrote:
> We have a Postgresqlv14.8 server, client use Postgresql JDBC connections,
> today,
> our server see a lot of “SubtransBuffer” and “SubtransSLRU” wait_event.
> Could you help direct me what’s the possible cause and how to resolve
On Thu, 2024-02-01 at 10:23 +0100, Dirk Krautschick wrote:
> I have run a test with pgbench against two cloud vendors (settings,
> parameters almost the same).
> Both Postgres (or whatever they do internally when they call it as Postgres
> offering, NOT Aurora or so :-) )
>
> I have got a
Hi,
We have a Postgresqlv14.8 server, client use Postgresql JDBC connections,
today, our server see a lot of "SubtransBuffer" and "SubtransSLRU" wait_event.
Could you help direct me what's the possible cause and how to resolve this
waits ?
Thanks,
James
Hi Heikki!
I made some modifications as you requested:
I have modified the program, now DISCARD ALL is issued within the program,
at the end.
I have added all headers to ps aux output so anyone can see the memory
growth I am refering to.
I now connect directly to postgrres,
I run now 50
Our case is 1) we use PL/PGSQL procedure1-->procedure2 (update table
;commit); 2) application JDBC client call procedure1 (it's a long running
job, sometimes it could last > 1hours). During this time window, other
Postgresql JDBC clients (100-200) coming in in same time , then