--=-B23nqlQkj8mkIxGzz0XE
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2003-10-28 at 18:49, Tom Lane wrote:
Very well.. Would it be enough simply to fix it so it does work? Remove
the S functionality and allow pg_catalog to work like a normal schema.

--=-B23nqlQkj8mkIxGzz0XE
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQA/nwdg6DETLow6vwwRAlTtAJ9aaKIax4JLCnMj13lk3vOwD7AgdQ CeKBcP
3HgffqkFwQppgcwb/MfFmJ4=
=pERi
-----END PGP SIGNATURE-----

--=-B23nqlQkj8mkIxGzz0XE--

--=-YxGGwuT2+mfOQnAFI/9Z
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2003-10-28 at 19:34, scott.marlowe wrote:
=46rom the search_path certainly -- but we can we teach the difference
between implicit and explicit to the *is_visible functions?

--=-YxGGwuT2+mfOQnAFI/9Z
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQA/nzJk6DETLow6vwwRAnBVAJ0eVn/XQnnnS0Ikkith8M+LVshrugCfW8RK
bbFok0oJum0paSJVXH5e2tc=
=qOMN
-----END PGP SIGNATURE-----

--=-YxGGwuT2+mfOQnAFI/9Z--

On Tue, 28 Oct 2003, Tom Lane wrote:

It seems a good compromise then would be that if "pg_catalog" is in your
search path, then do the old fashioned completion, i.e. p<tab> will list
everything in both pg_catalog and the other schemas in your search path.

Afterall, the system catalog kind of "hitchhikes" along for a ride in your
search path. Most users aren't interested in the system catalogs, so
having them suddenly show up when you just wanted the phonebook table is
kinda a bother for them.

Is it possible to remove the implicit search path of pg_catalog from a
psql session without it breaking lots of stuff? If not, then it's kind of
ugly to the user to have no way to get the system from proffering
pg_catalog tables when they have no interest in them. If so, then why
make it part of the default?




---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org)

On Tue, 28 Oct 2003, Tom Lane wrote:

Me, hardly ever use them :-) So I can assume that removing the implicit
pg_catalog from the search path is a "bad thing."

In that case, does my proposed solution of having to implicitly include
pg_catalog in your search path to get it to be seen by tab completion as
just another schema make sense?


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match