From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Invalid YAML output from EXPLAIN |
Date: | 2010-06-09 16:57:50 |
Message-ID: | AANLkTimhFyXt7BZC0JRuX1nkn1HwIYCKgN7sREWcP3TF@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 9 June 2010 17:52, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Jun 9, 2010 at 12:25 PM, 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: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.
>
> It seemed to me, in particular, that someone might use a # symbol,
> like "# of Iterations".
>
Then the resulting XML tagname would be invalid too
I think they would soon realise/be told that it was a bad idea.
Dean
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-06-09 16:58:48 | Re: Invalid YAML output from EXPLAIN |
Previous Message | Robert Haas | 2010-06-09 16:52:55 | Re: Invalid YAML output from EXPLAIN |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-06-09 16:58:11 | Re: hstore ==> and deprecate => |
Previous Message | David E. Wheeler | 2010-06-09 16:54:24 | Re: hstore ==> and deprecate => |