From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Why schema of table is removed from explain? |
Date: | 2011-09-01 20:42:51 |
Message-ID: | 20110901204251.GA23649@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Sep 01, 2011 at 04:39:06PM -0400, Tom Lane wrote:
> hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> > On Thu, Sep 01, 2011 at 04:24:59PM -0400, Tom Lane wrote:
> >> The non-plain-text output formats provide that sort of detail, if you
> >> need it.
>
> > Which is great, but why can't we have it in plain text too?
>
> It's frequently unnecessary, and horizontal space is precious in the
> plain-text format.
Well, I understand that adding "public." usually wouldn't be any good,
but what about representing the table name as oid::regclass does? i.e.
adds schema only if table is in schema that is not in search_path?
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Raghavendra | 2011-09-01 22:04:47 | pgfoundry.org is not accessible |
Previous Message | Scott Marlowe | 2011-09-01 20:41:13 | Re: How to get around this limitation (ALTER DATABASE db SET search_path = ...) |