Re: Drop "leaked" resources in sqljson/sqljson_queryfuncs regression tests

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tristan Partin" <tristan(at)partin(dot)io>
Cc: "pgsql-hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Drop "leaked" resources in sqljson/sqljson_queryfuncs regression tests
Date: 2026-08-21 23:06:23
Message-ID: 4114184.1787353583@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Tristan Partin" <tristan(at)partin(dot)io> writes:
> Found these "leaks" while doing some other work in the SQL/JSON area.
> Did some analysis to find that this should be backpatched through 17.

You sure those aren't intentional? One use of the regression
database's ending state is to serve as a test case for pg_upgrade,
so we like to leave around objects that are unique in some way.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2026-08-21 23:39:37 Re: Reduce memory overheads for storing a Memoize tuple
Previous Message Tristan Partin 2026-08-21 22:59:01 Drop "leaked" resources in sqljson/sqljson_queryfuncs regression tests