From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Rod Taylor <rbt(at)zort(dot)ca>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Temp tables are curious creatures.... |
Date: | 2002-04-30 10:37:24 |
Message-ID: | 1020163044.29163.2.camel@taru.tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2002-04-30 at 03:35, Tom Lane wrote:
> Rod Taylor <rbt(at)zort(dot)ca> writes:
> > Appears psql needs to know how to differentiate between it's own temp
> > tables and those of another connection.
>
> More generally, psql is as yet clueless about schemas.
>
> regression=# create schema foo;
> CREATE
> regression=# create schema bar;
> CREATE
> regression=# create table foo.tab1 (f1 int);
> CREATE
> regression=# create table bar.tab1 (f2 int);
> CREATE
> regression=# \d tab1
> Table "tab1"
> Column | Type | Modifiers
> --------+---------+-----------
> f1 | integer |
> f2 | integer |
>
> This is ... um ... wrong. I am not real sure what the right behavior
> is, however. Should \d accept patterns like schema.table (and how
> should its wildcard pattern matching fit with that?) If you don't
> specify a schema, should it only show tables visible in your search
> path?
Yes.
For me the intuitive answer would be
regression=# \d tab1
Table "foo.tab1"
Column | Type | Modifiers
--------+---------+-----------
f1 | integer |
Table "bar.tab1"
Column | Type | Modifiers
--------+---------+-----------
f2 | integer |
i.e. default wildcarding of missing pieces
-------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2002-04-30 11:09:57 | Re: Temp tables are curious creatures.... |
Previous Message | Karel Zak | 2002-04-30 08:29:47 | Re: Syscache/relcache invalidation event callbacks |