Re: BUG #16171: Potential malformed JSON in explain output

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: depesz(at)depesz(dot)com, Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16171: Potential malformed JSON in explain output
Date: 2020-02-04 18:08:46
Message-ID: 19959.1580839726@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

I wrote:
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> I guess I'm leaning towards backpatching, but it's not entirely clear-cut.

> That's where I stand too. I'll wait a day or so to see if anyone
> else comments; but if not, I'll back-patch.

Hearing no objections, done that way.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Vik Fearing 2020-02-05 02:03:04 Re: BUG #16242: convert_tuple_* not handling missing values correctly
Previous Message Jehan-Guillaume de Rorthais 2020-02-04 17:39:06 FK violation in partitioned table after truncating a referenced partition

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2020-02-04 18:11:59 Re: Index only scan and ctid
Previous Message Konstantin Knizhnik 2020-02-04 16:47:47 Re: [Proposal] Global temporary tables