Re: Temporarily suspend a user account?

From: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Temporarily suspend a user account?
Date: 2015-02-06 23:01:11
Message-ID: CAKFQuwY2o5xve6+XOd99XkMxKp7q-+wcLV_=7FBHVsg1+wdRiQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Feb 6, 2015 at 3:55 PM, Felipe Gasper [via PostgreSQL] <
ml-node+s1045698n5837008h72(at)n5(dot)nabble(dot)com> wrote:

> On 6 Feb 2015 4:51 PM, David G Johnston wrote:
>
> > On Fri, Feb 6, 2015 at 3:41 PM, Felipe Gasper [via PostgreSQL] <[hidden
> > email] </user/SendEmail.jtp?type=node&node=5837007&i=0>>wrote:
> >
> >
> > So, this works when I do it manually, but not when I script it.
> >
> > Is it possible that this change doesn’t take effect immediately? Is
> > there any way to tell when it does (besides just waiting until login
> > attempts fail)?
> >
> >
> > ​It should take effect when you commit the transaction in which you
> > perform the update...
> >
> > The active sessions would remain logged in but future attempts to login
> > would fail.
> >
>
> Yeah now I’m wondering if DBD::Pg is doing some weird caching.
>
> Anyhow, I’ll figure it out. Thank you! :)
> ​
>


Connection pool sessions are likely remaining connected to the database
longer than your application.
​..​

Dave

--
View this message in context: http://postgresql.nabble.com/Temporarily-suspend-a-user-account-tp5836978p5837009.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jerry Sievers 2015-02-06 23:04:17 Re: Temporarily suspend a user account?
Previous Message Felipe Gasper 2015-02-06 22:55:03 Re: Temporarily suspend a user account?