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 15:14:14
Message-ID: 25213.1276096454@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:03 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I still agree with Dean's original proposal: always quote the values of
>> strings.

> I'd still rather rip the format out entirely than do that.

I'd be on board with that too ;-)

> Dean's
> proposal was based on the idea that it would be safe to quote only the
> values and not the keys, which is not something I care to bank on.

Why not? Surely we can restrict EXPLAIN's set of key names to be safe.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dean Rasheed 2010-06-09 15:15:23 Re: Invalid YAML output from EXPLAIN
Previous Message Tom Lane 2010-06-09 15:08:22 Re: Bad optimizer data for xml (WAS: xml data type implications of no =)

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2010-06-09 15:15:23 Re: Invalid YAML output from EXPLAIN
Previous Message Heikki Linnakangas 2010-06-09 15:09:02 Re: Streaming Replication: Checkpoint_segment and wal_keep_segments on standby