Re: PostgreSQL Hosting
От | Thomas F. O'Connell |
---|---|
Тема | Re: PostgreSQL Hosting |
Дата | |
Msg-id | 18CA7D14-DF3C-4C4F-8A89-8B3C6A196B15@sitening.com обсуждение исходный текст |
Ответ на | Re: PostgreSQL Hosting ("Thomas F. O'Connell" <tfo@sitening.com>) |
Список | pgsql-general |
In my haste, I neglected to update the name of this view in my post to pg_database from its original definition as pg_db, which was the original name of the hacked view.
The point is that we want pg_catalog.pg_database to be superseded by public.pg_database from the point of view of both the user and pg_dump.
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005
On Jul 11, 2005, at 11:39 AM, Thomas F. O'Connell wrote:
Then we ran into the problem of allowing users to dump their own databases, which requires access to pg_database that we're trying to prevent at the user level. So we're now setting our schema search path for all user-created databases to public, pg_catalog, $user. Then we're creating a view called pg_database as:CREATE OR REPLACE VIEW pg_db ASSELECT oid, *FROM pg_databaseWHERE datname=(select current_user)
В списке pgsql-general по дате отправления: