When looking for a table, a user will always search their own schema first, then the public schema. When combined with table inheritance, this allows the creation of user-specific tables that isolate a user’s data but can still be included in aggregate queries by selecting from the master table.
The statement: ‘COPY tablename FROM STDIN;’ performs an INSERT of data received from the client, but does not obey RULEs ON INSERT to a view. It will still activate triggers, but unfortunately, creating triggers on views is currently beyond my skill level.
