| From: | Amul Sul <sulamul(at)gmail(dot)com> |
|---|---|
| To: | James Sewell <james(dot)sewell(at)jirotech(dot)com> |
| Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, 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 04:41:13 |
| Message-ID: | CAAJ_b94czoEydNS9DP74AHus7TaCV2SU-VqOp+vm_FkRpfowLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Dec 6, 2021 at 6:11 AM James Sewell <james(dot)sewell(at)jirotech(dot)com> wrote:
>>
>> 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.
>
+1, I too like the idea. The patch doesn't seem to be doing any heavy
lifting, I think that much overhead should be acceptable.
Regards,
Amul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2021-12-06 05:03:10 | Re: ssl_crl_file Certificate Revocation List doesn't work for postgresql 11 |
| Previous Message | James Sewell | 2021-12-06 00:40:41 | Re: Max connections reached without max connections reached |