| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | bianpan2016(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15541: Use after release in PQprint |
| Date: | 2018-12-07 18:15:24 |
| Message-ID: | 20181207181524.bm7gkj4jhc6rgdmh@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 2018-Dec-07, Tom Lane wrote:
> It still seems worth fixing in HEAD, in case anyone ever tries to
> remove that restriction; but I'm no longer feeling that we need
> to back-patch it.
I wonder why don't we just remove PQprint altogether.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-12-07 18:25:25 | Re: BUG #15541: Use after release in PQprint |
| Previous Message | Tom Lane | 2018-12-07 18:02:30 | Re: BUG #15541: Use after release in PQprint |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Finnerty | 2018-12-07 18:18:15 | Re: Adding support for a fully qualified column-name in UPDATE ... SET |
| Previous Message | Tom Lane | 2018-12-07 18:02:30 | Re: BUG #15541: Use after release in PQprint |