From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: EXPLAIN omits schema? |
Date: | 2007-06-13 14:45:17 |
Message-ID: | 467002FD.5000802@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> As already noted, it'd usually be clutter in lines that are too long
> already. Also, conditionally adding a schema name isn't very good
> because it makes life even more complicated for programs that are
> parsing EXPLAIN output (yes, there are some).
Well, yes - that's precisely what pgAdmin does, which is why I'd want to
see the schema name all the time. Up until now though all we've done is
graphically represent the plan, so the object names haven't really been
an issue. To take that further and allow the user to drill down to
further information, or to provide tools to help tune queries we need to
know for certain what table we're dealing with.
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-06-13 14:49:18 | Re: EXPLAIN omits schema? |
Previous Message | Gregory Stark | 2007-06-13 14:44:41 | Re: EXPLAIN omits schema? |