Re: CREATE RULE problem/question requesting workaround - Mailing list pgsql-general

From Tom Lane
Subject Re: CREATE RULE problem/question requesting workaround
Date
Msg-id 22637.1070818741@sss.pgh.pa.us
Whole thread Raw
In response to Re: CREATE RULE problem/question requesting workaround  (Chris Travers <chris@travelamericas.com>)
Responses Re: CREATE RULE problem/question requesting workaround  (Chris Travers <chris@travelamericas.com>)
List pgsql-general
Chris Travers <chris@travelamericas.com> writes:
> Adding every table as a view is not going to be likely to be feasible
> since it will involve a major maintenance nightmare.  Depending on
> requirements, we may look at allowing most of the database to be
> readable to all users, but this is not ideal and I am looking for
> maintainable workarounds.

Is it really not possible to express what you need with plain old SQL
permissions?  It seems like you are going out of your way to avoid the
obvious solution.

            regards, tom lane

pgsql-general by date:

Previous
From: Chris Travers
Date:
Subject: Re: CREATE RULE problem/question requesting workaround
Next
From: Greg Stark
Date:
Subject: Re: postgresql locks the whole table!