-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> 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.
I need something other than RelationIsVisible for psql for the case
when someone says "\d foo" - I need to be able to decide which
"foo" table I should display: pg_temp_1.foo, public.foo, greg.foo,
etc... which schemas to search, and the order to do the searching,
is why some sort of access to current_schemas() is needed.
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200208021010
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9SpfEvJuQZxSWSsgRAmw/AJ0RZ2vbx2zDQlFrLwRyVkZ1kvQB0ACgwyqT
9xugxhqatGJrrDWzzfez114=
=GZtD
-----END PGP SIGNATURE-----
