| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | bianpan2016(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15541: Use after release in PQprint |
| Date: | 2018-12-07 18:25:25 |
| Message-ID: | 17168.1544207125@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jose fuenmayor | 2018-12-07 23:25:33 | Unsuscribe |
| Previous Message | Alvaro Herrera | 2018-12-07 18:15:24 | Re: BUG #15541: Use after release in PQprint |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lætitia Avrot | 2018-12-07 18:48:39 | Re: Alter table documentation page (again) |
| Previous Message | Jim Finnerty | 2018-12-07 18:18:15 | Re: Adding support for a fully qualified column-name in UPDATE ... SET |