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-03 14:15:42
Message-ID: 5439.1580739342@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2020-02-03 14:24:50 Re: BUG #16240: The now() function is populating different date time than expected
Previous Message Arseny Sher 2020-02-03 13:46:05 Re: ERROR: subtransaction logged without previous top-level txn record

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-02-03 14:34:56 Re: Add %x to PROMPT1 and PROMPT2
Previous Message Stephen Frost 2020-02-03 14:07:09 Re: Complete data erasure