Horton
Menu

RE: Postgresql JDBC process consumes more memory with partition tables update delete

James Pang (chaolpan) <chaolpan@cisco.com>

View thread
From: "James Pang (chaolpan)" <chaolpan@cisco.com>
To: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
Cc: "pgsql-jdbc@lists.postgresql.org" <pgsql-jdbc@lists.postgresql.org>
Date: 2022-09-08T08:24:03Z
Lists: pgsql-performance

Attachments

Please check attached.

Thanks,
James
From: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
Sent: Thursday, September 8, 2022 3:05 PM
To: James Pang (chaolpan) <chaolpan@cisco.com>
Cc: pgsql-jdbc@lists.postgresql.org
Subject: Re: Postgresql JDBC process consumes more memory with partition tables update delete

> > Yesterday, when workload test, a lot of Postgresql JDBC connections
> > use 150-160MB memory , so we got ERROR: out of memory

Would you please share a reproducer? (e.g. DDL for the table, test code)

Have you tried capturing memory context information for the backend that consumes memory?
https://wiki.postgresql.org/wiki/Developer_FAQ#Examining_backend_memory_use

Vladimir

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix recovery_prefetch with low maintenance_io_concurrency.