postgres-xc-developers Mailing List for Postgres-XC

We should output an error message as well if the drop failed. In addition, since it cannot be wrapped in 2PC, we may have to consider a utility to cleanup partially dropped databases, but execute direct could do that, we just need to document it, and fix execute direct.


Sent from my IPhone

On Nov 26, 2010, at 5:53 AM, Michael Paquier <mic...@gm...> wrote:

> This seems to be linked with the pooler connections.
> Drop database does not work correctly if you don't empty pool before dropping it.
> 
> You should do something like:
> \c postgres
> clean connection to all for database dbt1;
> drop database dbt1;
> create database dbt1;
> 
> Have a look at the commit 54a648a3ffe7f8fc0273295ee17e91cebcb34948 in git repository for more details.
> 
> I admit that we need to call automatically pool cleaning when dropping a database.
> This is not done yet. We should commit a fix soon to support that.
> 
> Regards,
> 
> -- 
> Michael Paquier
> http://michaelpq.users.sourceforge.net
> 
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

This seems to be linked with the pooler connections.
Drop database does not work correctly if you don't empty pool before
dropping it.

You should do something like:
\c postgres
clean connection to all for database dbt1;
drop database dbt1;
create database dbt1;

Have a look at the commit 54a648a3ffe7f8fc0273295ee17e91cebcb34948 in git
repository for more details.

I admit that we need to call automatically pool cleaning when dropping a
database.
This is not done yet. We should commit a fix soon to support that.

Regards,

-- 
Michael Paquier
http://michaelpq.users.sourceforge.net

Dears,

If I drop a database, it seems that content of database isn't really
deleted.

The steps as follows:
1.postgres=# drop database dbt1;
DROP DATABASE
2.postgres=# create database dbt1;
CREATE DATABASE
3.postgres=# \c dbt1
psql (8.4.3)
You are now connected to database "dbt1".
4.dbt1=# create table t(a int);
CREATE TABLE
5.dbt1=# insert into t values(1);
INSERT 0 1
6.dbt1=# \c postgres
psql (8.4.3)
You are now connected to database "postgres".
7.postgres=# drop database dbt1;
DROP DATABASE
8.postgres=# create database dbt1;
CREATE DATABASE
9.postgres=# \c dbt1
psql (8.4.3)
You are now connected to database "dbt1".
10.dbt1=# \d
        List of relations
 Schema | Name | Type  |  Owner
--------+------+-------+----------
 public | t    | table | postgres
(1 row)
11.dbt1=# select * from t;
 a
---
 1
(1 row)


Regards,
Benny