| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Guillermo Carrasco <guillermo(dot)carrasco(at)scilifelab(dot)se>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: REVOKE command not working as expected |
| Date: | 2013-11-12 15:13:24 |
| Message-ID: | 5993.1384269204@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Tue, Nov 12, 2013 at 7:58 AM, Guillermo Carrasco
> <guillermo(dot)carrasco(at)scilifelab(dot)se> wrote:
>> The problem is that sometimes (apparently random), even after having invoked
>> EVOKE CONNECT ON DATABASE \"$DB\" FROM PUBLIC;, when the scripts starts
>> dumping, it fails because it says that there are some active connections.
> Revoking connection does not disconnect currently connected clients.
My money is on autovacuum.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2013-11-12 15:19:00 | Re: REVOKE command not working as expected |
| Previous Message | Guillermo Carrasco | 2013-11-12 15:02:37 | Re: REVOKE command not working as expected |