pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: vitstn@gmail.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17422: Memory leak
Date: Tue, 1 Mar 2022 12:21:12 -0800
Message-ID: <20220301202112.f6dc5ooory7tqdir@alap3.anarazel.de> (raw)
In-Reply-To: <17422-6a5f554d27f8ff39@postgresql.org>
References: <17422-6a5f554d27f8ff39@postgresql.org>

On 2022-03-01 17:06:02 +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      17422
> Logged by:          Vitaly Stoyan
> Email address:      vitstn@gmail.com
> PostgreSQL version: 13.6
> Operating system:   any
> Description:        
> 
> https://github.com/postgres/postgres/blob/REL_13_STABLE/src/backend/utils/adt/json.c#L83
> 
> It seems memory allocated by palloc for lex variable isn't freed

In a lot of places we free memory in bulk by resetting memory contexts. See
https://github.com/postgres/postgres/blob/master/src/backend/utils/mmgr/README

Greetings,

Andres Freund





view thread (2+ messages)

Message-ID: <20220301202112.f6dc5ooory7tqdir@alap3.anarazel.de>
Permalink:  ../20220301202112.f6dc5ooory7tqdir@alap3.anarazel.de/
Also on:    postgresql.org/message-id/20220301202112.f6dc5ooory7tqdir@alap3.anarazel.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: andres@anarazel.de, vitstn@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #17422: Memory leak
  In-Reply-To: <20220301202112.f6dc5ooory7tqdir@alap3.anarazel.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox