Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C70D6475925 for ; Wed, 20 Nov 2002 16:16:09 -0500 (EST) Received: from bob.samurai.com (bob.samurai.com [205.207.28.75]) by postgresql.org (Postfix) with ESMTP id D2A664758FE for ; Wed, 20 Nov 2002 16:16:07 -0500 (EST) Received: from tokyo.samurai.com (DU150.N224.ResNet.QueensU.CA [130.15.224.150]) by bob.samurai.com (Postfix) with ESMTP id 15B2A1D8C; Wed, 20 Nov 2002 16:16:03 -0500 (EST) To: Francisco Reyes Cc: pgsql General List Subject: Re: Closing inactive connections OR user connections limits References: <20021120135451.V30106-100000@zoraida.natserv.net> From: Neil Conway In-Reply-To: <20021120135451.V30106-100000@zoraida.natserv.net> Date: 20 Nov 2002 16:15:57 -0500 Message-ID: <873cpw54du.fsf@mailbox.samurai.com> Lines: 32 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/869 X-Sequence-Number: 33290 Francisco Reyes writes: > On 20 Nov 2002, Neil Conway wrote: > > Not if the connection is made to the database as the PostgreSQL > > superuser. > > So this would be new to 7.3. Right? Yes. > Right now if there are connections open "vacuum full" will wait from those > connectins to close, even if the vacuum is done from the superuser. Erm, no -- VACUUM FULL doesn't block on connections, it blocks waiting to acquire locks. Whether or not a client is allowed to connect to the database has no relation to the locks the client can acquire once they've connected. > > Heh, no where at the moment, as there wasn't isn't any documentation > > on this new feature :-) Attached is a patch that adds some (also sent > > to -patches). > > So there will be a way to reserve connectinos for the super-user, but will > there be a way to limit number of connection per user? Not in 7.3, AFAIK. Cheers, Neil -- Neil Conway || PGP Key ID: DB3C29FC