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 CAANVwEtvHvG+HHBT_LkOOs2UcSb=s8nPcmmYYtqi7wOw5B+ptA@mail.gmail.com
Whole thread Raw
In response to Re: Max connections reached without max connections reached  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Max connections reached without max connections reached  (Amul Sul <sulamul@gmail.com>)
List 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.

pgsql-general by date:

Previous
From: Daniel Frey
Date:
Subject: Re: libpq: Which functions may hang due to network issues?
Next
From: Amul Sul
Date:
Subject: Re: Max connections reached without max connections reached