Re: Invalid YAML output from EXPLAIN

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Dean Rasheed" <dean(dot)a(dot)rasheed(at)gmail(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Invalid YAML output from EXPLAIN
Date: 2010-06-09 15:23:03
Message-ID: 4C0F6B8702000025000320D8@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:

> So that just leaves this sort of thing:
>
> explain (format yaml) select * from foo as "123";

What about other quoted identifiers? If I recall correctly, a
quoted identifier can contain *any* characters (although a quote
must be represented as two adjacent quotes).

test=# create schema "0";
CREATE SCHEMA
test=# create table "0"."123" ("456" int primary key);
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"123_pkey" for table "123"
CREATE TABLE
test=# explain (format yaml) select * from "0"."123" where "456" =
'789';
QUERY PLAN
-----------------------------------
- Plan: +
Node Type: Index Scan +
Scan Direction: Forward +
Index Name: "\"123_pkey\"" +
Relation Name: 123 +
Alias: 123 +
Startup Cost: 0.00 +
Total Cost: 8.27 +
Plan Rows: 1 +
Plan Width: 4 +
Index Cond: "(\"456\" = 789)"
(1 row)

Also, the trailing spaces in this format (stripped from this email
to avoid odd spacing) are more than a little annoying.

-Kevin

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Sabino Mullane 2010-06-09 15:57:17 Re: [BUGS] Invalid YAML output from EXPLAIN
Previous Message Dean Rasheed 2010-06-09 15:15:23 Re: Invalid YAML output from EXPLAIN

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Sabino Mullane 2010-06-09 15:57:17 Re: [BUGS] Invalid YAML output from EXPLAIN
Previous Message Dean Rasheed 2010-06-09 15:15:23 Re: Invalid YAML output from EXPLAIN