| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | "Dave Page" <dpage(at)postgresql(dot)org>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: EXPLAIN omits schema? |
| Date: | 2007-06-13 18:01:38 |
| Message-ID: | 14728.1181757698@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Arguably this is a bug if it's causing pg_admin difficulties in parsing the
> output. Even for a user in an environment where, for example, he has several
> identical schemas and may be accidentally getting a different table than he's
> expecting the current output is ambiguous.
> Attached is a small patch which adds this conditionally on a guc that
> pg_admin or other GUI tools could set, leaving it unchanged for users.
That makes things *worse* not better, since now tools would have to
deal with both possibilities.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2007-06-13 18:05:23 | Re: Controlling Load Distributed Checkpoints |
| Previous Message | Tom Lane | 2007-06-13 17:52:10 | Re: \d omits schema on inherited tables (Was: EXPLAIN omits schema?) |