Excerpts from Tom Lane's message of lun mar 19 16:53:49 -0300 2012: > This connects somewhat to the discussions we've had in the past about > trying to get not-intended-for-public-use functions out of the standard > search path. Not that you want to put a full visibility check into the > tab-completion query,
I'm rather of the contrary opinion -- surely if we're going to complete function names, we should only complete those that are in schemas in the path; similarly for column names. (BTW I didn't check but does this completion work if I schema-qualify a column name?) > but if it could simply exclude a "pg_private" > namespace, that probably wouldn't be too expensive. +1 -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
