Re: small psql patch - show Schema name for \dt \dv \dS

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Joe Conway <mail(at)joeconway(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: small psql patch - show Schema name for \dt \dv \dS
Date: 2002-08-02 18:26:45
Message-ID: 200208021826.g72IQjv07507@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane wrote:
> >> Backend pid doesn't solve this issue, because the temp schema name for a
> >> logged-in user is based on MyBackendId, not pid, i.e. your temp schema
> >> name is something like pg_temp_1 when MyBackendId = 1, etc. It would be
> >> easy enough to write a function exposing this, the question is whether
> >> it is desirable to expose it?
>
> I see no reason to do so at all.
>
> What you want is not the BackendId; what you want is the temp schema
> name, and current_schemas() can tell you that.
>
> But so far I haven't seen any convincing argument why any client query
> would really want to look at current_schemas(), either. What you
> actually want to know about is visibility, and computing that from
> current_schemas() is quite an expensive proposition. I think what
> we need to expose is RelationIsVisible and friends, not BackendId.

Well, if we are going to reach 7.3, we had better figure out what we are
doing in this area. Let's start talking.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2002-08-02 18:39:42 Re: [HACKERS] DROP COLUMN round 4
Previous Message Tom Lane 2002-08-02 15:25:05 Re: small psql patch - show Schema name for \dt \dv \dS