Re: Schemas: status report, call for developers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ian Barwick <barwick(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Schemas: status report, call for developers
Date: 2002-05-01 04:38:37
Message-ID: 4870.1020227917@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

Ian Barwick <barwick(at)gmx(dot)net> writes:
> How can I restrict the query to the schemas in the
> current search path, i.e. the schema names returned
> by SELECT current_schemas() ?

Well, this is the issue open for public discussion.

We could define some function along the lines of
"is_visible_table(oid) returns bool", and then you could use
that as a WHERE clause in your query. But I'm worried about
the performance implications --- is_visible_table() would have
to do several retail probes of the system tables, and I don't
see any way to optimize that across hundreds of table OIDs.

I have a nagging feeling that this could be answered by defining
a view on pg_class that only shows visible tables ... but I don't
quite see how to define that efficiently, either. Ideas anyone?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ross J. Reedstrom 2002-05-01 04:49:10 Re: [INTERFACES] Schemas: status report, call for developers
Previous Message Tom Lane 2002-05-01 04:09:29 Re: [INTERFACES] Schemas: status report, call for developers

Browse pgsql-interfaces by date

  From Date Subject
Next Message Ross J. Reedstrom 2002-05-01 04:49:10 Re: [INTERFACES] Schemas: status report, call for developers
Previous Message Tom Lane 2002-05-01 04:09:29 Re: [INTERFACES] Schemas: status report, call for developers