Re: Invalid explain output for multi-plan statements

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Invalid explain output for multi-plan statements
Дата
Msg-id 603c8f070912140959l1832d025me6abab21561e4186@mail.gmail.com
обсуждение исходный текст
Ответ на Invalid explain output for multi-plan statements  ("Greg Sabino Mullane" <greg@turnstep.com>)
Ответы Re: Invalid explain output for multi-plan statements  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-bugs
On Mon, Dec 14, 2009 at 12:32 PM, Greg Sabino Mullane <greg@turnstep.com> w=
rote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
> The new explain formats break if you have a multi-query statement.
> I don't have time to fix at the moment, but I'll try and explain
> the problem. For YAML, the forced leading space in all output
> means that the first "- Plan:" has two spaces, and all other ones
> have a single space. This leads to an inconsistent indentation
> error when parsing. For JSON, I'm not sure where the exact problem
> lies, but it also will not parse as it produces something like this:
>
> [
> =A0{
> =A0 ...plan 1
> =A0},,
> =A0{
> =A0 ...plan2
> =A0}
> ]
>
> The XML output looks valid, but I've not tried to parse it.
>
> To duplicate:
>
> CREATE TABLE abc(a int);
> INSERT INTO abc VALUES (1);
> CREATE TABLE def(a int);
> CREATE RULE foo AS ON UPDATE TO abc DO ALSO SELECT 1 FROM def;
>
> EXPLAIN (format YAML) UPDATE abc SET a=3Da;
> EXPLAIN (format JSON) UPDATE abc SET a=3Da;
> EXPLAIN (format XML) UPDATE abc SET a=3Da;

I will fix this, unless someone else beats me to it.

...Robert

В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Greg Sabino Mullane"
Дата:
Сообщение: Invalid explain output for multi-plan statements
Следующее
От: "Greg Johnson"
Дата:
Сообщение: BUG #5243: Segmentation fault when sending null to crypt();