Re: memory leak in pgoutput

From: by Yang <mobile(dot)yang(at)outlook(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>
Subject: Re: memory leak in pgoutput
Date: 2024-11-19 07:08:26
Message-ID: DM3PR84MB344267C77FE5CF0612E59C6FE3202@DM3PR84MB3442.NAMPRD84.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> By the way, if possible, could you send an updated version of the
> patch to show what you have in mind?
Yeah, here is the new patch:

I have verifed that this patch works for REL_[15-17]_STABLE and master.
The memory consumption of "logical replication cache context" remains
consistently at 112 MB during the benchmark mentioned above.
> sysbench oltp_write_only --db-driver=pgsql \
> --pgsql-port=5432 \
> --pgsql-db=postgres \
> --pgsql-user=postgres \
> --tables=15000 --table_size=100 \
> --report-interval=1 \
> --threads=10 run \
> --time=180

Attachment Content-Type Size
v2-0001-Fix-memory-leak-in-pgoutput.patch application/octet-stream 1.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shlok Kyal 2024-11-19 07:11:46 Re: Disallow UPDATE/DELETE on table with unpublished generated column as REPLICA IDENTITY
Previous Message Bertrand Drouvot 2024-11-19 06:52:40 Re: fix deprecation mention for age() and mxid_age()