Re: Add tracking of backend memory allocated to pg_stat_activity - Mailing list pgsql-hackers

From Reid Thompson
Subject Re: Add tracking of backend memory allocated to pg_stat_activity
Date
Msg-id 25c6f9005107807a850da4304f7bc47da031eb1b.camel@crunchydata.com
Whole thread Raw
In response to Re: Add tracking of backend memory allocated to pg_stat_activity  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
On Thu, 2023-01-05 at 14:13 -0600, Justin Pryzby wrote:
>
> I suggest to close the associated CF entry.

Closed with status of Withdrawn. If that is invalid, please advise.

> (Also, the people who participated in this thread may want to be
> included in the other thread going forward.)

Explicitly adding previously missed participants to Cc: - that conversation/patches are being consolidated to
the thread  "Add the ability to limit the amount of memory that can be allocated to backends"
 https://www.postgresql.org/message-id/bd57d9a4c219cc1392665fd5fba61dde8027b3da.camel@crunchydata.com



Thanks,
Reid

--
Reid Thompson
Senior Software Engineer
Crunchy Data, Inc.

reid.thompson@crunchydata.com
www.crunchydata.com




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ExecRTCheckPerms() and many prunable partitions (checkAsUser)
Next
From: Michail Nikolaev
Date:
Subject: Re: BUG: Postgres 14 + vacuum_defer_cleanup_age + FOR UPDATE + UPDATE