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

Mason Sharp msharp at translattice.com
Mon Sep 22 09:23:16 PDT 2014


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.postgres-xl.org/private.cgi/postgres-xl-general-postgres-xl.org/attachments/20140922/a73f3f2b/attachment.htm>


More information about the postgres-xl-general mailing list