[Postgres-xl-general] Can't drop database

Koichi Suzuki koichi.dbms at gmail.com
Thu Sep 25 18:41:46 PDT 2014


Did you try to restart whole cluster before you drop a database?
This will enforce to cleanup all the connections to the dropping
database.

Regards;
---
Koichi Suzuki


2014-09-23 3:17 GMT+09:00 Aaron Jackson <ajackson at revionics.com>:
> 1 server - Amazon - m2
> 1 gtm - on m2 instance
>
> 3 servers - Amazon i2.xlarge
> 3 coordinators - one per server
> 6 datanodes - two per server
> 3 gtm proxies - one per server
>
> I realize this is difficult to create from the limited information I have
> given you so I am working on crafting a test case with non-proprietary data
> so that you can have something a bit more tangible to work with.
>
> Aaron
> ________________________________
> From: Mason Sharp [msharp at translattice.com]
> Sent: Monday, September 22, 2014 11:23 AM
> To: Aaron Jackson
> Cc: postgres-xl-general at lists.sourceforge.net
> Subject: Re: [Postgres-xl-general] Can't drop database
>
>
> On Sat, Sep 20, 2014 at 12:51 AM, Aaron Jackson <ajackson at revionics.com>
> wrote:
>>
>> This problem appears to have reappeared.  Simple process that uses about 4
>> threads to load data into the database concurrently.  At one point, the load
>> failed due to timeout and I began to query pg_stat_activity on the
>> underlying datanodes.
>>
>> All 6 datanodes had the following query reported ...
>>
>> RESET ALL;RESET SESSION AUTHORIZATION;RESET transaction_isolation;
>>
>> Coord2 and Coord3 also reported the same query.  Coord1 had no such query
>> running.
>>
>> When I tried to drop the database I was told there was 1 prepared
>> transaction using the database.  Now, I will go through and hunt down the
>> errant node and reset it but this is exactly what happened last time.  And
>> it only appears to happen when I'm doing dataload via copy on more than one
>> table concurrently.
>
> OK, we can try to reproduce this. So, 4 concurrent data loads, each via a
> different coordinator, and each into a different table? Any other
> information, like, GTM Proxy used? Any other concurrent activity present on
> the cluster?
>
> Thanks,
>
> Mason
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xl-general mailing list
> Postgres-xl-general at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/postgres-xl-general
>




More information about the postgres-xl-general mailing list