From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: bianpan2016@163.com
Cc: pgsql-bugs@lists.postgresql.org
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: BUG #15541: Use after release in PQprint
Date: Fri, 07 Dec 2018 13:25:25 -0500
Message-ID: <17168.1544207125@sss.pgh.pa.us> (raw)
In-Reply-To: <20181207181524.bm7gkj4jhc6rgdmh@alvherre.pgsql>
References: <20181207181524.bm7gkj4jhc6rgdmh@alvherre.pgsql>
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> I wonder why don't we just remove PQprint altogether.
Yeah, I was wondering that too. AFAICS the whole of fe-print.c
is dead code so far as our own usage is concerned. Is there any
evidence that outside code is using PQprint, PQprintTuples, or
PQdisplayTuples? (The latter two aren't even documented...)
Still, I'm not sure if we can remove them outright without it
being considered a library compatibility break by some distros.
regards, tom lane
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: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, bianpan2016@163.com, pgsql-bugs@lists.postgresql.org, pgsql-hackers@lists.postgresql.org
Subject: Re: BUG #15541: Use after release in PQprint
In-Reply-To: <17168.1544207125@sss.pgh.pa.us>
* 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