Re: Invalid YAML output from EXPLAIN
От | Robert Haas |
---|---|
Тема | Re: Invalid YAML output from EXPLAIN |
Дата | |
Msg-id | AANLkTinTojXatqqOWgBL_e5683RLF26e4BpykwM6REjo@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Invalid YAML output from EXPLAIN (Dean Rasheed <dean.a.rasheed@gmail.com>) |
Ответы |
Re: Invalid YAML output from EXPLAIN
Re: Invalid YAML output from EXPLAIN |
Список | pgsql-bugs |
On Wed, Jun 9, 2010 at 12:57 PM, Dean Rasheed <dean.a.rasheed@gmail.com> wr= ote: > On 9 June 2010 17:52, Robert Haas <robertmhaas@gmail.com> wrote: >> On Wed, Jun 9, 2010 at 12:25 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> Robert Haas <robertmhaas@gmail.com> writes: >>>> On Wed, Jun 9, 2010 at 11:14 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>>>> Why not? =A0Surely we can restrict EXPLAIN's set of key names to be s= afe. >>> >>>> It seems to me that it would be easy for a future patch to break this >>>> by accident. >>> >>> Really? =A0What likely key names would be in need of quoting? =A0I 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. Hmm, you're right. Maybe we should go with your approach, then. --=20 Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-bugs по дате отправления: