I'd be glad to hear any opinions/suggestions.
Many thanks to everyone who responded!
Mike
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
On Wed, Jun 24, 2009 at 9:52 AM, Tom Lane wrote:
> "Albe Laurenz" writes:
>> Robert Haas wrote:
>>> I don't think this is true. You can use SET SESSION AUTHORIZATION,
>>> right?
>
>> You are right, I overlooked that.
>> It is restricted to superusers though.
>
> That sort of thing is only workabl
"Albe Laurenz" writes:
> Robert Haas wrote:
>> I don't think this is true. You can use SET SESSION AUTHORIZATION,
>> right?
> You are right, I overlooked that.
> It is restricted to superusers though.
That sort of thing is only workable if you have trustworthy client code
that controls what q
Robert Haas wrote:
> > You cannot keep the connection and change users.
> > A change of database user always means a new connection and a new
> > backend process.
>
> I don't think this is true. You can use SET SESSION AUTHORIZATION,
> right?
You are right, I overlooked that.
It is restricte
On Jun 24, 2009, at 4:32 AM, "Albe Laurenz"
wrote:
Mike Ivanov wrote:
Please help me to make a decision on how to manage users.
For some reason it is easier in the project I'm working on to split
data
by schemes and assign them to Postgres' users (I mean those created
with
CREATE USER)
Mike Ivanov wrote:
> Please help me to make a decision on how to manage users.
>
> For some reason it is easier in the project I'm working on to split data
> by schemes and assign them to Postgres' users (I mean those created with
> CREATE USER) rather than support 'owner' fields referring to a
Hi there,
Please help me to make a decision on how to manage users.
For some reason it is easier in the project I'm working on to split data
by schemes and assign them to Postgres' users (I mean those created with
CREATE USER) rather than support 'owner' fields referring to a global
users tab
