Peter Eisentraut wrote:
On tor, 2009-12-10 at 17:20 -0500, Andrew Dunstan wrote:
Some time later it came up again, this time when someone wanted to use a
readonly database (hence no pg_dump required) with an application and
wanted to keep the database layout and the source code of stored
On tor, 2009-12-10 at 17:20 -0500, Andrew Dunstan wrote:
> Some time later it came up again, this time when someone wanted to use a
> readonly database (hence no pg_dump required) with an application and
> wanted to keep the database layout and the source code of stored
> functions hidden as the
Tom Lane wrote:
Andrew Dunstan writes:
The other day I returned idly to thinking about some work I did a few
years ago on creating a totally unprivileged user, i.e. one with not
even public permissions.
And the point would be what exactly?
Well, when
Andrew Dunstan writes:
> The other day I returned idly to thinking about some work I did a few
> years ago on creating a totally unprivileged user, i.e. one with not
> even public permissions.
And the point would be what exactly?
regards, tom lane
--
Sent via pgsql-ha
The other day I returned idly to thinking about some work I did a few
years ago on creating a totally unprivileged user, i.e. one with not
even public permissions. The work I did then involved hacking the
pg_catalog, information_schema and public schemas and their contents.
Unfortunately, it do
