Re: Max connections reached without max connections reached - Mailing list pgsql-general

From James Sewell
Subject Re: Max connections reached without max connections reached
Date
Msg-id CAANVwEt_yZtL5N9vnbRaswo2u7cVzC7iHTKQE8fpgcsH3Wy7Aw@mail.gmail.com
Whole thread Raw
In response to Re: Max connections reached without max connections reached  (James Sewell <james.sewell@jirotech.com>)
Responses Re: Max connections reached without max connections reached  (James Sewell <james.sewell@jirotech.com>)
List pgsql-general

I'm guessing this won't be back-patched? Is it possible to somehow read this information from a C function?
 

Ok it is possible, I've got a C extension up and running which hooks ExecutorStart, then once for each TX ( I monitor the nesting depth like in pg_stat_statements, and only attach at the top level) attaches a sub transaction callback, tracking start subtransaction events and incrementing a counter / keeping track of the worst offenders in a hashmap.

This seems to work very well - but I've got a question. How many sub transactions would you expect the following anon block and function to create respectively? The first seems to report 9, and the second 10 - is this expected? It feels like it might be - I just want to make sure.

do $$
begin
   for counter in 1..10 loop
   begin
   INSERT INTO a VALUES (counter);
exception
when no_data_found then  raise exception 'gosh';
  end;
   end loop;
end; 
$$


CREATE OR REPLACE FUNCTION public.create_subtransactions()
 RETURNS void
 LANGUAGE plpgsql
AS $function$
begin
   for counter in 1..10 loop
     begin
       INSERT INTO a VALUES (counter);
     exception
       when no_data_found then  raise exception 'gosh';
     end;
  end loop;
end;
$function$


- James


The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: How best to turn select result into options like 'a|b|c''
Next
From: James Sewell
Date:
Subject: Re: Max connections reached without max connections reached