Re: Max connections reached without max connections reached

From: James Sewell <james(dot)sewell(at)jirotech(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Max connections reached without max connections reached
Date: 2021-12-06 00:40:41
Message-ID: CAANVwEtvHvG+HHBT_LkOOs2UcSb=s8nPcmmYYtqi7wOw5B+ptA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> Agreed with both points. What about we add, subxid count and overflow
> status in LocalPgBackendStatus and through that, we can show in
> pg_stat_activity. That way we don't have to report it ever and
> whenever the user is running pg_stat_activity they can fetch it
> directly from "proc->subxidStatus", along with fetching the proc.xid
> and proc.xmin. Does this make sense?
>

Not sure about the overhead and performance aspects, but I like this
solution from a functional point of view.

--
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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Amul Sul 2021-12-06 04:41:13 Re: Max connections reached without max connections reached
Previous Message Daniel Frey 2021-12-05 20:32:24 Re: libpq: Which functions may hang due to network issues?