On Mon, Dec 14, 2009 at 12:32 PM, Greg Sabino Mullane <g...@turnstep.com> wrote:
>
> -----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:
>
> [
> {
> ...plan 1
> },,
> {
> ...plan2
> }
> ]
>
> 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=a;
> EXPLAIN (format JSON) UPDATE abc SET a=a;
> EXPLAIN (format XML) UPDATE abc SET a=a;
I will fix this, unless someone else beats me to it.
...Robert
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
