On Fri, Feb 6, 2015 at 3:55 PM, Felipe Gasper [via PostgreSQL] <[hidden email]> 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.