From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:05:28 |
Message-ID: | AANLkTinFObBWQIss0m1-CPkZW7ZNc6NAmeaOYbtA9Lhh@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Wed, Jun 9, 2010 at 11:14 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
It seems to me that it would be easy for a future patch to break this
by accident.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-09 16:25:18 | Re: Invalid YAML output from EXPLAIN |
Previous Message | Greg Sabino Mullane | 2010-06-09 15:57:17 | Re: [BUGS] Invalid YAML output from EXPLAIN |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-09 16:09:36 | Re: Idea for getting rid of VACUUM FREEZE on cold pages |
Previous Message | Tom Lane | 2010-06-09 16:02:27 | Re: hstore ==> and deprecate => |