From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com> |
Cc: | pgsql-general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Pg stuck at 100% cpu, for multiple days |
Date: | 2021-08-30 14:36:21 |
Message-ID: | 20210830143621.GA23857@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Aug 30, 2021 at 07:57:26PM +0530, Vijaykumar Jain wrote:
> related? i was kind of expecting debezium when i saw cdc and java, but
> DBZ-1596 Fix open resources while initializing publication by Naros · Pull
> Request #1120 · debezium/debezium (github.com)
> <https://github.com/debezium/debezium/pull/1120>
> [DBZ-1596] AWS RDS Performance Insights screwed a little by non-closed
> statement in "SELECT COUNT(1) FROM pg_publication" - Red Hat Issue Tracker
> <https://issues.redhat.com/browse/DBZ-1596>
> I may be wrong, but just in case, FYI.
I'll pass this information to people that use the tool that fetches data
from DB, but is still makes me ask: why does Pg end up in such place,
where it doesn't do any syscalls, doesn't accept pg_terminate_backend(),
and is using 100% of cpu?
Best regards,
depesz
From | Date | Subject | |
---|---|---|---|
Next Message | Pól Ua Laoínecháin | 2021-08-30 14:43:54 | Re: Arrays - selecting (and not removing) duplicates... |
Previous Message | Vijaykumar Jain | 2021-08-30 14:27:26 | Re: Pg stuck at 100% cpu, for multiple days |