Re: [Postgres-xc-developers] A bug for drop database!

[Mason S. <mas...@en...>]

On 11/8/10 5:13 AM, mei le wrote:
> Dears,
> the steps as follows:
> postgres=# create database dbt1;
> CREATE DATABASE
> postgres=# \c dbt1
> psql (8.4.3)
> You are now connected to database "dbt1".
> dbt1=# create table t(a int);
> CREATE TABLE
> dbt1=# \c postgres
> psql (8.4.3)
> You are now connected to database "postgres".
> postgres=# drop database dbt1;
> ERROR:  database "dbt1" is being accessed by other users
> DETAIL:  There are 1 other session(s) using the database.
> In addition,it's ok to drop databse if I didn't create any object in 
> database dbt1.
>                                                                                     
> regards,
>                                                                                         
> Benny
>
>

Thanks, this is a known issue.  The issue is that the pooler is holding 
on to the connections. Michael is  doing some work right now to clean 
pooler connections.  I think it should get committed sometime in the 
next week or so.

Thanks,

Mason

>
> ------------------------------------------------------------------------------
> The Next 800 Companies to Lead America's Growth: New Video Whitepaper
> David G. Thomson, author of the best-selling book "Blueprint to a
> Billion" shares his insights and actions to help propel your
> business during the next growth cycle. Listen Now!
> http://p.sf.net/sfu/SAP-dev2dev
>
>
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>    


-- 
Mason Sharp
EnterpriseDB Corporation
The Enterprise Postgres Company


This e-mail message (and any attachment) is intended for the use of
the individual or entity to whom it is addressed. This message
contains information from EnterpriseDB Corporation that may be
privileged, confidential, or exempt from disclosure under applicable
law. If you are not the intended recipient or authorized to receive
this for the intended recipient, any use, dissemination, distribution,
retention, archiving, or copying of this communication is strictly
prohibited. If you have received this e-mail in error, please notify
the sender immediately by reply e-mail and delete this message.