Re: Implications of having large number of users

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Robert Haas *EXTERN*" <robertmhaas(at)gmail(dot)com>
Cc: "Mike Ivanov *EXTERN*" <mikei(at)activestate(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Implications of having large number of users
Date: 2009-06-24 13:02:57
Message-ID: D960CB61B694CF459DCFB4B0128514C202FF667D@exadv11.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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 restricted to superusers though.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2009-06-24 13:52:34 Re: Implications of having large number of users
Previous Message Dave North 2009-06-24 12:43:23 Nested Loop "Killer" on 8.1