Re: Invalid YAML output from EXPLAIN

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Invalid YAML output from EXPLAIN
Date: 2010-06-09 16:25:18
Message-ID: 26416.1276100718@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Jun 9, 2010 at 11:14 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Why not? Surely we can restrict EXPLAIN's set of key names to be safe.

> It seems to me that it would be easy for a future patch to break this
> by accident.

Really? What likely key names would be in need of quoting? I can't
imagine accepting a field name that contains punctuation or leading
or trailing whitespace, for example.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dean Rasheed 2010-06-09 16:38:53 Re: Invalid YAML output from EXPLAIN
Previous Message Robert Haas 2010-06-09 16:05:28 Re: Invalid YAML output from EXPLAIN

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-06-09 16:30:24 Re: hstore ==> and deprecate =>
Previous Message Tom Lane 2010-06-09 16:09:36 Re: Idea for getting rid of VACUUM FREEZE on cold pages