Re: Invalid YAML output from EXPLAIN
| От | Robert Haas |
|---|---|
| Тема | Re: Invalid YAML output from EXPLAIN |
| Дата | |
| Msg-id | AANLkTinZxNrOw0gZbkZem0o0cUpBemngtL-VDvYf3G9s@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Invalid YAML output from EXPLAIN (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Invalid YAML output from EXPLAIN
|
| Список | pgsql-bugs |
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 saf= e. > >> 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". Maybe I'm being paranoid. --=20 Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-bugs по дате отправления: