postgres-xc-general Mailing List for Postgres-XC (Page 71)

>
> > Hi Folks,
> > Is there already a perl and python module for Postgres XC ? IF yes where
> > could i download it ? If no, how could I get Python/Perl functions work ?
>
Just one point of detail.
Even if plpython and plperl functions have not been tested yet, I would
suspect they work correctly as long as no more than one SQL query is used
inside the function as argument values are fetche dthe same way for plpgsql,
plperl and plpythin functions.
-- 
Michael Paquier
http://michael.otacoo.com

So far, we've not tested plpython and plperl.    We're now woking to support SQL functions and pl/pgSQL functions.   In the current head, they work if they contain only one sql statement.   Development team is discussing how to support multi-statement planner.

Because XC's external interface is alomst the same as original PG, I expect they may work with the above restriction.

It's very helpful if you try one of them.

Best Regards;
---
Koichi Suzuki

On Tue, 24 May 2011 14:19:27 +0200
Eric Ndengang <eri...@af...> wrote:

> Hi Folks,
> Is there already a perl and python module for Postgres XC ? IF yes where 
> could i download it ? If no, how could I get Python/Perl functions work ?
> regards
> 
> -- 
> Eric Ndengang
> Datenbankadministrator
> 
> Affinitas GmbH  |  Kohlfurter Straße 41/43  |  10999 Berlin  |  Germany
> email: eri...@af...  | tel: +49.(0)30. 991 949 5 0  |  www.edarling.de
> 
> Geschäftsführer: Lukas Brosseder, David Khalil, Kai Rieke, Christian Vollmann
> Eingetragen beim Amtsgericht Berlin, HRB 115958
> 
> Real People:          www.edarling.de/echte-paare
> Real Love:            www.youtube.de/edarling
> Real Science:         www.edarling.org
> 
> 
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery, 
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now. 
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
> 

Hi Folks,
Is there already a perl and python module for Postgres XC ? IF yes where 
could i download it ? If no, how could I get Python/Perl functions work ?
regards

-- 
Eric Ndengang
Datenbankadministrator

Affinitas GmbH  |  Kohlfurter Straße 41/43  |  10999 Berlin  |  Germany
email: eri...@af...  | tel: +49.(0)30. 991 949 5 0  |  www.edarling.de

Geschäftsführer: Lukas Brosseder, David Khalil, Kai Rieke, Christian Vollmann
Eingetragen beim Amtsgericht Berlin, HRB 115958

Real People:          www.edarling.de/echte-paare
Real Love:            www.youtube.de/edarling
Real Science:         www.edarling.org

Ok, thanks for the follow-up.

Lionel F.

Le 19 mai 2011 à 17:28, Michael Paquier <mic...@gm...> a
écrit :

I still need to review this patch.
Once it is corrected and committed, feel free to use the head.

On Thu, May 19, 2011 at 11:23 PM, Lionel Frachon
<lio...@gm...>wrote:

> Good news, as far as I see, the patch is working ok ! :)
>
> (Not reviewed the whole code to know if it meets the quality
> criterias, but will keep it for now)
>
> Lionel F.
>
>
>
> 2011/5/19 Michael Paquier <mic...@gm...>:
> > This is a PGXC-side problem for sure, JDBC may not be involved.
> > The fact is that we are currently having problems with JDBC driver like
> in
> > bug 3299211 at table creation.
> > The cause of that is we haven't done so many tests with it.
> >
> > Howver, we got a patch on the JDBC bug there. It has not yet been
> reviewed:
> >
> http://sourceforge.net/tracker/?func=detail&aid=3299211&group_id=311227&atid=1310232
> >
> > If you try to apply it, does your problem disappear?
> >
> > On Thu, May 19, 2011 at 5:53 PM, Lionel Frachon <
> lio...@gm...>
> > wrote:
> >>
> >> Hello,
> >>
> >> I'm trying to run BenchmarkSQL against a (for the moment) single node
> >> on 0.9.4, however I face some connection issues.
> >>
> >> Running the create table script, here is what I get :
> >>
> >> ------------- ExecJDBC Start Date = Thu May 19 10:41:14 CEST
> >> 2011-------------
> >> driver=org.postgresql.Driver
> >> conn=jdbc:postgresql://10.114.12.39:26001/testperfs
> >> user=pgxc
> >> password=******
> >> commandFile=sqlTableCreates
> >> -------------------------------------------------
> >>
> >>
> >>
> >> create table warehouse (
> >> w_id        integer   not null,
> >> w_ytd       decimal(12,2),
> >> w_tax       decimal(4,4),
> >> w_name      varchar(10),
> >> w_street_1  varchar(20),
> >> w_street_2  varchar(20),
> >> w_city      varchar(20),
> >> w_state     char(2),
> >> w_zip       char(9)
> >> );
> >> -- SQL Success: Runtime = 33 ms --
> >>
> >> commit;
> >> -- SQL Runtime Exception -----------------------------------------
> >> DBMS SqlCode=0  DBMS Msg=
> >>  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur.
> >> ------------------------------------------------------------------
> >>
> >>
> >>
> >> create table district (
> >> d_w_id       integer       not null,
> >> d_id         integer       not null,
> >> d_ytd        decimal(12,2),
> >> d_tax        decimal(4,4),
> >> d_next_o_id  integer,
> >> d_name       varchar(10),
> >> d_street_1   varchar(20),
> >> d_street_2   varchar(20),
> >> d_city       varchar(20),
> >> d_state      char(2),
> >> d_zip        char(9)
> >> );
> >> -- SQL Runtime Exception -----------------------------------------
> >> DBMS SqlCode=0  DBMS Msg=
> >>  This connection has been closed.
> >> ------------------------------------------------------------------
> >>
> >> and all the lasting table are not created, while the first one is.
> >>
> >> I updated the provided BenchmarkSQL jdbc driver (from
> >> postgresql-8.0.309.jdbc3.jar to the latest
> >> postgresql-9.0-801.jdbc3.jar) but no luck in this.
> >>
> >> What looks strange to me is
> >> "
> >> -- SQL Runtime Exception -----------------------------------------
> >> DBMS SqlCode=0  DBMS Msg=
> >>  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur."
> >>
> >> (it means An I/O error occured while sending data to the server") but
> >> the SqlCode is 0. I tried to remove the commit line, same effect.
> >>
> >> Is there any possibility to get debug info on this to know what's
> >> happening, or have hints to the proper method (java libs on client
> >> side, ....)
> >>
> >> Thanks for your help
> >>
> >> Regards.
> >>
> >> Lionel F.
> >>
> >
> >
> > --
> > Michael Paquier
> > http://michael.otacoo.com
> >
>



-- 
Michael Paquier
http://michael.otacoo.com

I still need to review this patch.
Once it is corrected and committed, feel free to use the head.

On Thu, May 19, 2011 at 11:23 PM, Lionel Frachon
<lio...@gm...>wrote:

> Good news, as far as I see, the patch is working ok ! :)
>
> (Not reviewed the whole code to know if it meets the quality
> criterias, but will keep it for now)
>
> Lionel F.
>
>
>
> 2011/5/19 Michael Paquier <mic...@gm...>:
> > This is a PGXC-side problem for sure, JDBC may not be involved.
> > The fact is that we are currently having problems with JDBC driver like
> in
> > bug 3299211 at table creation.
> > The cause of that is we haven't done so many tests with it.
> >
> > Howver, we got a patch on the JDBC bug there. It has not yet been
> reviewed:
> >
> http://sourceforge.net/tracker/?func=detail&aid=3299211&group_id=311227&atid=1310232
> >
> > If you try to apply it, does your problem disappear?
> >
> > On Thu, May 19, 2011 at 5:53 PM, Lionel Frachon <
> lio...@gm...>
> > wrote:
> >>
> >> Hello,
> >>
> >> I'm trying to run BenchmarkSQL against a (for the moment) single node
> >> on 0.9.4, however I face some connection issues.
> >>
> >> Running the create table script, here is what I get :
> >>
> >> ------------- ExecJDBC Start Date = Thu May 19 10:41:14 CEST
> >> 2011-------------
> >> driver=org.postgresql.Driver
> >> conn=jdbc:postgresql://10.114.12.39:26001/testperfs
> >> user=pgxc
> >> password=******
> >> commandFile=sqlTableCreates
> >> -------------------------------------------------
> >>
> >>
> >>
> >> create table warehouse (
> >> w_id        integer   not null,
> >> w_ytd       decimal(12,2),
> >> w_tax       decimal(4,4),
> >> w_name      varchar(10),
> >> w_street_1  varchar(20),
> >> w_street_2  varchar(20),
> >> w_city      varchar(20),
> >> w_state     char(2),
> >> w_zip       char(9)
> >> );
> >> -- SQL Success: Runtime = 33 ms --
> >>
> >> commit;
> >> -- SQL Runtime Exception -----------------------------------------
> >> DBMS SqlCode=0  DBMS Msg=
> >>  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur.
> >> ------------------------------------------------------------------
> >>
> >>
> >>
> >> create table district (
> >> d_w_id       integer       not null,
> >> d_id         integer       not null,
> >> d_ytd        decimal(12,2),
> >> d_tax        decimal(4,4),
> >> d_next_o_id  integer,
> >> d_name       varchar(10),
> >> d_street_1   varchar(20),
> >> d_street_2   varchar(20),
> >> d_city       varchar(20),
> >> d_state      char(2),
> >> d_zip        char(9)
> >> );
> >> -- SQL Runtime Exception -----------------------------------------
> >> DBMS SqlCode=0  DBMS Msg=
> >>  This connection has been closed.
> >> ------------------------------------------------------------------
> >>
> >> and all the lasting table are not created, while the first one is.
> >>
> >> I updated the provided BenchmarkSQL jdbc driver (from
> >> postgresql-8.0.309.jdbc3.jar to the latest
> >> postgresql-9.0-801.jdbc3.jar) but no luck in this.
> >>
> >> What looks strange to me is
> >> "
> >> -- SQL Runtime Exception -----------------------------------------
> >> DBMS SqlCode=0  DBMS Msg=
> >>  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur."
> >>
> >> (it means An I/O error occured while sending data to the server") but
> >> the SqlCode is 0. I tried to remove the commit line, same effect.
> >>
> >> Is there any possibility to get debug info on this to know what's
> >> happening, or have hints to the proper method (java libs on client
> >> side, ....)
> >>
> >> Thanks for your help
> >>
> >> Regards.
> >>
> >> Lionel F.
> >>
> >
> >
> > --
> > Michael Paquier
> > http://michael.otacoo.com
> >
>



-- 
Michael Paquier
http://michael.otacoo.com

Good news, as far as I see, the patch is working ok ! :)

(Not reviewed the whole code to know if it meets the quality
criterias, but will keep it for now)

Lionel F.



2011/5/19 Michael Paquier <mic...@gm...>:
> This is a PGXC-side problem for sure, JDBC may not be involved.
> The fact is that we are currently having problems with JDBC driver like in
> bug 3299211 at table creation.
> The cause of that is we haven't done so many tests with it.
>
> Howver, we got a patch on the JDBC bug there. It has not yet been reviewed:
> http://sourceforge.net/tracker/?func=detail&aid=3299211&group_id=311227&atid=1310232
>
> If you try to apply it, does your problem disappear?
>
> On Thu, May 19, 2011 at 5:53 PM, Lionel Frachon <lio...@gm...>
> wrote:
>>
>> Hello,
>>
>> I'm trying to run BenchmarkSQL against a (for the moment) single node
>> on 0.9.4, however I face some connection issues.
>>
>> Running the create table script, here is what I get :
>>
>> ------------- ExecJDBC Start Date = Thu May 19 10:41:14 CEST
>> 2011-------------
>> driver=org.postgresql.Driver
>> conn=jdbc:postgresql://10.114.12.39:26001/testperfs
>> user=pgxc
>> password=******
>> commandFile=sqlTableCreates
>> -------------------------------------------------
>>
>>
>>
>> create table warehouse (
>> w_id        integer   not null,
>> w_ytd       decimal(12,2),
>> w_tax       decimal(4,4),
>> w_name      varchar(10),
>> w_street_1  varchar(20),
>> w_street_2  varchar(20),
>> w_city      varchar(20),
>> w_state     char(2),
>> w_zip       char(9)
>> );
>> -- SQL Success: Runtime = 33 ms --
>>
>> commit;
>> -- SQL Runtime Exception -----------------------------------------
>> DBMS SqlCode=0  DBMS Msg=
>>  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur.
>> ------------------------------------------------------------------
>>
>>
>>
>> create table district (
>> d_w_id       integer       not null,
>> d_id         integer       not null,
>> d_ytd        decimal(12,2),
>> d_tax        decimal(4,4),
>> d_next_o_id  integer,
>> d_name       varchar(10),
>> d_street_1   varchar(20),
>> d_street_2   varchar(20),
>> d_city       varchar(20),
>> d_state      char(2),
>> d_zip        char(9)
>> );
>> -- SQL Runtime Exception -----------------------------------------
>> DBMS SqlCode=0  DBMS Msg=
>>  This connection has been closed.
>> ------------------------------------------------------------------
>>
>> and all the lasting table are not created, while the first one is.
>>
>> I updated the provided BenchmarkSQL jdbc driver (from
>> postgresql-8.0.309.jdbc3.jar to the latest
>> postgresql-9.0-801.jdbc3.jar) but no luck in this.
>>
>> What looks strange to me is
>> "
>> -- SQL Runtime Exception -----------------------------------------
>> DBMS SqlCode=0  DBMS Msg=
>>  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur."
>>
>> (it means An I/O error occured while sending data to the server") but
>> the SqlCode is 0. I tried to remove the commit line, same effect.
>>
>> Is there any possibility to get debug info on this to know what's
>> happening, or have hints to the proper method (java libs on client
>> side, ....)
>>
>> Thanks for your help
>>
>> Regards.
>>
>> Lionel F.
>>
>
>
> --
> Michael Paquier
> http://michael.otacoo.com
>

OK I see.
Thanks for your try.
It is good to know that more and more people are trying XC with JDBC,
so we definitely need to focus on it more than present.

I'll try myself to look at the potential problems.

On Thu, May 19, 2011 at 8:36 PM, Lionel Frachon <lio...@gm...>wrote:

> Hello,
>
> thanks Michael for your quick reply. However, continuing the tests,
> the problem appears wider than table creation (issues appears aswell
> when creating the test case indexes). The client (even hosted on very
> same server and connecting through 127.0.0.1) still complains about
> loosing connection.
> I did some workaround by executing the creation scripts through local
> coordinator (psql), which runs ok - that gives an argument to your
> point.
>
> I'll patch the version I use (the git May 13th one) and give you feedback
> asap.
>
> If I could be of any help regarding jdbc testing, let me know.
>


-- 
Michael Paquier
http://michael.otacoo.com

Hello,

thanks Michael for your quick reply. However, continuing the tests,
the problem appears wider than table creation (issues appears aswell
when creating the test case indexes). The client (even hosted on very
same server and connecting through 127.0.0.1) still complains about
loosing connection.
I did some workaround by executing the creation scripts through local
coordinator (psql), which runs ok - that gives an argument to your
point.

I'll patch the version I use (the git May 13th one) and give you feedback asap.

If I could be of any help regarding jdbc testing, let me know.

Regards

Lionel FRACHON
---------------------
Database Administrator
Open Source Team Leader
THALES - Critical Information Systems


2011/5/19 Michael Paquier <mic...@gm...>:
> This is a PGXC-side problem for sure, JDBC may not be involved.
> The fact is that we are currently having problems with JDBC driver like in
> bug 3299211 at table creation.
> The cause of that is we haven't done so many tests with it.
>
> Howver, we got a patch on the JDBC bug there. It has not yet been reviewed:
> http://sourceforge.net/tracker/?func=detail&aid=3299211&group_id=311227&atid=1310232
>
> If you try to apply it, does your problem disappear?
>
> On Thu, May 19, 2011 at 5:53 PM, Lionel Frachon <lio...@gm...>
> wrote:
>>
>> Hello,
>>
>> I'm trying to run BenchmarkSQL against a (for the moment) single node
>> on 0.9.4, however I face some connection issues.
>>
>> Running the create table script, here is what I get :
>>
>> ------------- ExecJDBC Start Date = Thu May 19 10:41:14 CEST
>> 2011-------------
>> driver=org.postgresql.Driver
>> conn=jdbc:postgresql://10.114.12.39:26001/testperfs
>> user=pgxc
>> password=******
>> commandFile=sqlTableCreates
>> -------------------------------------------------
>>
>>
>>
>> create table warehouse (
>> w_id        integer   not null,
>> w_ytd       decimal(12,2),
>> w_tax       decimal(4,4),
>> w_name      varchar(10),
>> w_street_1  varchar(20),
>> w_street_2  varchar(20),
>> w_city      varchar(20),
>> w_state     char(2),
>> w_zip       char(9)
>> );
>> -- SQL Success: Runtime = 33 ms --
>>
>> commit;
>> -- SQL Runtime Exception -----------------------------------------
>> DBMS SqlCode=0  DBMS Msg=
>>  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur.
>> ------------------------------------------------------------------
>>
>>
>>
>> create table district (
>> d_w_id       integer       not null,
>> d_id         integer       not null,
>> d_ytd        decimal(12,2),
>> d_tax        decimal(4,4),
>> d_next_o_id  integer,
>> d_name       varchar(10),
>> d_street_1   varchar(20),
>> d_street_2   varchar(20),
>> d_city       varchar(20),
>> d_state      char(2),
>> d_zip        char(9)
>> );
>> -- SQL Runtime Exception -----------------------------------------
>> DBMS SqlCode=0  DBMS Msg=
>>  This connection has been closed.
>> ------------------------------------------------------------------
>>
>> and all the lasting table are not created, while the first one is.
>>
>> I updated the provided BenchmarkSQL jdbc driver (from
>> postgresql-8.0.309.jdbc3.jar to the latest
>> postgresql-9.0-801.jdbc3.jar) but no luck in this.
>>
>> What looks strange to me is
>> "
>> -- SQL Runtime Exception -----------------------------------------
>> DBMS SqlCode=0  DBMS Msg=
>>  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur."
>>
>> (it means An I/O error occured while sending data to the server") but
>> the SqlCode is 0. I tried to remove the commit line, same effect.
>>
>> Is there any possibility to get debug info on this to know what's
>> happening, or have hints to the proper method (java libs on client
>> side, ....)
>>
>> Thanks for your help
>>
>> Regards.
>>
>> Lionel F.
>>
>
>
> --
> Michael Paquier
> http://michael.otacoo.com
>

Hi,

On top of that, what is the version you are using for your tests?
You have to know that ROLE queries are not fully supported in 0.9.4 because
Postgres-XC pooler is restricted to only one user in this version.
This restriction is not anymore in current HEAD code.
With 0.9.4 you can launch role queries, but it will not be possible to
launch queries if you connect with the new user name.

On Thu, May 19, 2011 at 7:48 PM, Abbas Butt <abb...@te...>wrote:

> Why do you need three coordinators? Each data node does not need a
> coordinator. One can suffice 3 data nodes, unless you need another for
> backup. I would suggest running the data node on the three servers and GTM
> and coordinator on the 4rth server.

Well, each user can design a cluster as he wants depending on his use case.
The point is that XC should work whatever the configuration used, even if we
think it is not the one showing good performance.

Regards,
-- 
Michael Paquier
http://michael.otacoo.com

Thanks for giving it a try. Why do you need three coordinators? Each data
node does not need a coordinator. One can suffice 3 data nodes, unless you
need another for backup. I would suggest running the data node on the three
servers and GTM and coordinator on the 4rth server.
Now Each coordinator and data node needs to know IP address and port of the
GTM. It is specified in the postgresql.conf file in the data folder of each
node in the section GTM CONNECTION.
Next each data node needs to know IP address and port of the coordinator.
This is specified again in postgresql.conf file in the data folder of each
data node in the section COORDINATORS.
Next each coordinator need to know IPs and ports of all data nodes. Again
this is specified in DATA NODES section of the postgresql.conf file in the
data folder of the coordinator.
Once you get all the warnings out of the way then give dump a try it should
work.

Best Regards
Abbas


On Thu, May 19, 2011 at 3:16 PM, Eric Ndengang <
eri...@af...> wrote:

> Hi folks,
> I 've  installed a Postgres XC instance (4 servers) with one GTM and
> three coordinators/datanodes . Three servers get 1 coodinator +
> datanode  each and the gtm has it own server.
> I started the GTM, nodes and coordinatoors as well , but some Warning
> notifications in Datanode Logs  occurs --> WARNING:  Do not have a GTM
> snapshot available
> Regarding the Installationsdocs the global schema dump hast to be run on
> the coordinator. I've tried it and got the following ERRORS :
> LOG:  failed to connect to data node
> WARNING:  can not connect to data node 2
> LOG:  failed to acquire connections
> STATEMENT:  CREATE ROLE drodriguez;
> ERROR:  Failed to get pooled connections
> STATEMENT:  CREATE ROLE drodriguez;
> ERROR:  role "drodriguez" does not exist
> STATEMENT:  ALTER ROLE drodriguez WITH NOSUPERUSER INHERIT NOCREATEROLE
> NOCREATEDB LOGIN PASSWORD 'md59d4b27232eeec39777ee0b08ed8387a7';
> LOG:  failed to connect to data node
> WARNING:  can not connect to data node 2
>
> but I could run a schema dump on all the data nodes. is it sufficient ?
>
> That why I want to know how to run a schema dump in Postgres XC.
> any help would be really appreciated
>
>
>
> --
> Eric Ndengang
> Datenbankadministrator
>
> Affinitas GmbH  |  Kohlfurter Straße 41/43  |  10999 Berlin  |  Germany
> email: eri...@af...  | tel: +49.(0)30. 991 949 5 0  |
>  www.edarling.de
>
> Geschäftsführer: Lukas Brosseder, David Khalil, Kai Rieke, Christian
> Vollmann
> Eingetragen beim Amtsgericht Berlin, HRB 115958
>
> Real People:          www.edarling.de/echte-paare
> Real Love:            www.youtube.de/edarling
> Real Science:         www.edarling.org
>
>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>

Hi folks,
I 've  installed a Postgres XC instance (4 servers) with one GTM and 
three coordinators/datanodes . Three servers get 1 coodinator + 
datanode  each and the gtm has it own server.
I started the GTM, nodes and coordinatoors as well , but some Warning 
notifications in Datanode Logs  occurs --> WARNING:  Do not have a GTM 
snapshot available
Regarding the Installationsdocs the global schema dump hast to be run on 
the coordinator. I've tried it and got the following ERRORS :
LOG:  failed to connect to data node
WARNING:  can not connect to data node 2
LOG:  failed to acquire connections
STATEMENT:  CREATE ROLE drodriguez;
ERROR:  Failed to get pooled connections
STATEMENT:  CREATE ROLE drodriguez;
ERROR:  role "drodriguez" does not exist
STATEMENT:  ALTER ROLE drodriguez WITH NOSUPERUSER INHERIT NOCREATEROLE 
NOCREATEDB LOGIN PASSWORD 'md59d4b27232eeec39777ee0b08ed8387a7';
LOG:  failed to connect to data node
WARNING:  can not connect to data node 2

but I could run a schema dump on all the data nodes. is it sufficient ?

That why I want to know how to run a schema dump in Postgres XC.
any help would be really appreciated



-- 
Eric Ndengang
Datenbankadministrator

Affinitas GmbH  |  Kohlfurter Straße 41/43  |  10999 Berlin  |  Germany
email: eri...@af...  | tel: +49.(0)30. 991 949 5 0  |  www.edarling.de

Geschäftsführer: Lukas Brosseder, David Khalil, Kai Rieke, Christian Vollmann
Eingetragen beim Amtsgericht Berlin, HRB 115958

Real People:          www.edarling.de/echte-paare
Real Love:            www.youtube.de/edarling
Real Science:         www.edarling.org

This is a PGXC-side problem for sure, JDBC may not be involved.
The fact is that we are currently having problems with JDBC driver like in
bug 3299211 at table creation.
The cause of that is we haven't done so many tests with it.

Howver, we got a patch on the JDBC bug there. It has not yet been reviewed:
http://sourceforge.net/tracker/?func=detail&aid=3299211&group_id=311227&atid=1310232

If you try to apply it, does your problem disappear?

On Thu, May 19, 2011 at 5:53 PM, Lionel Frachon <lio...@gm...>wrote:

> Hello,
>
> I'm trying to run BenchmarkSQL against a (for the moment) single node
> on 0.9.4, however I face some connection issues.
>
> Running the create table script, here is what I get :
>
> ------------- ExecJDBC Start Date = Thu May 19 10:41:14 CEST
> 2011-------------
> driver=org.postgresql.Driver
> conn=jdbc:postgresql://10.114.12.39:26001/testperfs
> user=pgxc
> password=******
> commandFile=sqlTableCreates
> -------------------------------------------------
>
>
>
> create table warehouse (
> w_id        integer   not null,
> w_ytd       decimal(12,2),
> w_tax       decimal(4,4),
> w_name      varchar(10),
> w_street_1  varchar(20),
> w_street_2  varchar(20),
> w_city      varchar(20),
> w_state     char(2),
> w_zip       char(9)
> );
> -- SQL Success: Runtime = 33 ms --
>
> commit;
> -- SQL Runtime Exception -----------------------------------------
> DBMS SqlCode=0  DBMS Msg=
>  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur.
> ------------------------------------------------------------------
>
>
>
> create table district (
> d_w_id       integer       not null,
> d_id         integer       not null,
> d_ytd        decimal(12,2),
> d_tax        decimal(4,4),
> d_next_o_id  integer,
> d_name       varchar(10),
> d_street_1   varchar(20),
> d_street_2   varchar(20),
> d_city       varchar(20),
> d_state      char(2),
> d_zip        char(9)
> );
> -- SQL Runtime Exception -----------------------------------------
> DBMS SqlCode=0  DBMS Msg=
>  This connection has been closed.
> ------------------------------------------------------------------
>
> and all the lasting table are not created, while the first one is.
>
> I updated the provided BenchmarkSQL jdbc driver (from
> postgresql-8.0.309.jdbc3.jar to the latest
> postgresql-9.0-801.jdbc3.jar) but no luck in this.
>
> What looks strange to me is
> "
> -- SQL Runtime Exception -----------------------------------------
> DBMS SqlCode=0  DBMS Msg=
>  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur."
>
> (it means An I/O error occured while sending data to the server") but
> the SqlCode is 0. I tried to remove the commit line, same effect.
>
> Is there any possibility to get debug info on this to know what's
> happening, or have hints to the proper method (java libs on client
> side, ....)
>
> Thanks for your help
>
> Regards.
>
> Lionel F.
>
>

-- 
Michael Paquier
http://michael.otacoo.com

Hello,

I'm trying to run BenchmarkSQL against a (for the moment) single node
on 0.9.4, however I face some connection issues.

Running the create table script, here is what I get :

------------- ExecJDBC Start Date = Thu May 19 10:41:14 CEST 2011-------------
driver=org.postgresql.Driver
conn=jdbc:postgresql://10.114.12.39:26001/testperfs
user=pgxc
password=******
commandFile=sqlTableCreates
-------------------------------------------------



create table warehouse (
w_id        integer   not null,
w_ytd       decimal(12,2),
w_tax       decimal(4,4),
w_name      varchar(10),
w_street_1  varchar(20),
w_street_2  varchar(20),
w_city      varchar(20),
w_state     char(2),
w_zip       char(9)
);
-- SQL Success: Runtime = 33 ms --

commit;
-- SQL Runtime Exception -----------------------------------------
DBMS SqlCode=0  DBMS Msg=
  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur.
------------------------------------------------------------------



create table district (
d_w_id       integer       not null,
d_id         integer       not null,
d_ytd        decimal(12,2),
d_tax        decimal(4,4),
d_next_o_id  integer,
d_name       varchar(10),
d_street_1   varchar(20),
d_street_2   varchar(20),
d_city       varchar(20),
d_state      char(2),
d_zip        char(9)
);
-- SQL Runtime Exception -----------------------------------------
DBMS SqlCode=0  DBMS Msg=
  This connection has been closed.
------------------------------------------------------------------

and all the lasting table are not created, while the first one is.

I updated the provided BenchmarkSQL jdbc driver (from
postgresql-8.0.309.jdbc3.jar to the latest
postgresql-9.0-801.jdbc3.jar) but no luck in this.

What looks strange to me is
"
-- SQL Runtime Exception -----------------------------------------
DBMS SqlCode=0  DBMS Msg=
  Une erreur d'entrée/sortie a eu lieu lors d'envoi vers le serveur."

(it means An I/O error occured while sending data to the server") but
the SqlCode is 0. I tried to remove the commit line, same effect.

Is there any possibility to get debug info on this to know what's
happening, or have hints to the proper method (java libs on client
side, ....)

Thanks for your help

Regards.

Lionel F.

Hi,

0.9.4 manuals and source tarball have been released there:
https://sourceforge.net/projects/postgres-xc/files/Version_0.9.4/
-- 
Thanks,

Michael Paquier
http://michael.otacoo.com

Hello

Thanks ! As i didn't notice the announce, i thought it was postponed a bit.

Thanks for the tip, i'll stick to head revision.

Regards

Lionel F.
Envoyé de mon mobile

Le 9 avr. 2011 à 04:14, Michael Paquier <mic...@gm...> a
écrit :

0.9.4 is already available in the GIT repository. It has been released last
week.
We still need to deliver tar files and manuals, I hope this can be made next
week.

But since important commits have been made in the repository the last couple
of days, I would recommend to use the current head if you want to make some
tests.

On Fri, Apr 8, 2011 at 11:38 PM, Lionel Frachon <lio...@gm...>wrote:

> Hello,
>
> as I saw recurring commits in the repository, would it be possible to have
> an update of the availability date of PG-XC 0.9.4, even estimated ?
>
> Many thanks for your answer.
>
> Regards
>
> Lionel Frachon
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>


-- 
Thanks,

Michael Paquier
http://michael.otacoo.com

0.9.4 is already available in the GIT repository. It has been released last
week.
We still need to deliver tar files and manuals, I hope this can be made next
week.

But since important commits have been made in the repository the last couple
of days, I would recommend to use the current head if you want to make some
tests.

On Fri, Apr 8, 2011 at 11:38 PM, Lionel Frachon <lio...@gm...>wrote:

> Hello,
>
> as I saw recurring commits in the repository, would it be possible to have
> an update of the availability date of PG-XC 0.9.4, even estimated ?
>
> Many thanks for your answer.
>
> Regards
>
> Lionel Frachon
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>


-- 
Thanks,

Michael Paquier
http://michael.otacoo.com

Hello,

as I saw recurring commits in the repository, would it be possible to have
an update of the availability date of PG-XC 0.9.4, even estimated ?

Many thanks for your answer.

Regards

Lionel Frachon

Thanks for your valuable answers, my test cluster is now working (worth
mentionning I was additionally mislead by unexpected /etc/hosts.allow set
up...)

Other notes below

Regards

2011/3/6 Michael Paquier <mic...@gm...>

> Hi Lionel,
>
> Just to complete a little bit the answers of my colleague...
>
> On Sat, Mar 5, 2011 at 3:36 PM, Abbas Butt <abb...@te...>wrote:
>
>> My actual setup is :
>>> pgxc1 for GTM, Coordinator and datanode
>>> pgxc2 for datanode only
>>>
>>
>> You mean you will have 2 computers, one will run GTM, Coordinator and 1st
>> datanode and the other the 2nd data node. If yes then this would be fine.
>>
>> BTW what Linux distribution will you be using?
>>
>
RedHat Enterprise 5.4 by now.



>
>>
>
>
>>
>>> 1.General : Is a coordinator needed for each node, or one coordinator
>>> 'to rule them all' can be setup ?
>>>
>> You can use one Coordinator with 100 Datanodes if you desire.
> It may be better if the ratio Coordinator/Datanode is close to 1, but we
> also found that if you set one Coordinator and one Datanode on the same
> machine, Coordinator was using 30% of ressources and Datanode 70%.
> With such numbers, a ratio of 0.5 is also possible.
>

Yes, I'm aiming to test, given your numbers, 1 Coordinator for 3 Datanodes,
summing up to ~20 machines (if possible with our infrastructure folks). The
breaking point may be the bandwidth (after the number of available hosts, of
course).


>
>>
>>>
>>> 2. Configuration :  What should be the differences between
>>> postgresql.conf in /datanode and /coordinator, if there are any?
>>
>> [...]
> You have also pooler connection parameters to set but I forgot all the
> names.
>

No issue, I'll try by myself. And tweaking this needs I'm ready to run
benchmarks, which is not the actual phase.


> For datanode, you have to take care of GTM connection parameter and
> pgxc_node_id (used to register on GTM).
>
> In your cluster you can have a Coordinator 1 and a Datanode 1 as the
> difference between node type is made when registering nodes on GTM.
>
>
>>
>>> Some
>>> portions are they ignored for a specific function (ex : coordinator vs
>>> datanode config, etc...)
>>> In this can pg_hba.conf & postgresql.conf be shared for the same
>>> server (maybe using symbolic links...)
>>>
>> No, you have to set up each postgresql.conf and pg_hba.conf for each node
> separately as each Coordinator and Datanode use different data folder.
>

I'm having pg_hba.conf same setup on all dirs/hosts for the moment, but for
the others, I've understood what you meant when the cluster was finally
running...


>
>>
>>> 3. GTM : I get on second node an "WARNING:  Do not have a GTM snapshot
>>> available", can this be related to previous config files/setup  ?
>>>
>> This error means that you didn't set up GTM connection parameters
> correctly.
>
>>
>>
>>>
>>> 4. Administration : are there ways of getting the online status of the
>>> nodes from one node to another
>>>
>>
>> This is currently under development. I can provide you details later.
>>
> Those experimental functionalities are located on a separate branch called
> ha_support in the GIT repo.
>

It would be of a great interest in terms of supportability in a company-wide
perspective. I'll give them a try if they're next to alpha status :)


>
> We are also thinking about adding some catalog extensions to allow
> coordinator to keep an eye on Datanodes as such a view process is linker to
> the connection pooling process.
>

Great idea.


> This is just a thought though.
> Now as we are focusing on code stability for the core, this is not a high
> priority.
> But as we merged with PostgreSQL 9.0, it may be possible in a close future
> to use XC with HOT Standby nodes. Current streaming replication is not
> synchronized so its usage is now limited in current XC.
>
> If you have any other questions, don't hesitate.
>

I never do :)

Regards

Lionel F.

Hi Lionel,

Just to complete a little bit the answers of my colleague...

On Sat, Mar 5, 2011 at 3:36 PM, Abbas Butt <abb...@te...> wrote:

> My actual setup is :
>> pgxc1 for GTM, Coordinator and datanode
>> pgxc2 for datanode only
>>
>
> You mean you will have 2 computers, one will run GTM, Coordinator and 1st
> datanode and the other the 2nd data node. If yes then this would be fine.
>
> BTW what Linux distribution will you be using?
>
> Please remember that for the first time gtm has to be started with -x
> option and it is better to start gtm before you initdb for the coordinator
> and the 2 data nodes. For successive runs you should skip -x option. As a
> general rule you should always start gtm first then the data nodes and then
> the coordinator.
>
Basically, you can initialize your data directory when you want.
The only point you have to take care is to start GTM before the other nodes
as when you start a node it tries to register on GTM.
After that it doesn't matter if you start Coordinators or Datanodes first.

For GTM startup, you have to set for the first time -x which permit to set
the first value of GXID GTM will feed to Postgres-XC nodes.
If for instance you stopped you cluster, you can restart GTM from the same
data folder as before with having to precise the first GXID value as this
value will be taken automatically from the GTM data folder if the file where
last GXID was written exists.


>
>> 1.General : Is a coordinator needed for each node, or one coordinator
>> 'to rule them all' can be setup ?
>>
> You can use one Coordinator with 100 Datanodes if you desire.
It may be better if the ratio Coordinator/Datanode is close to 1, but we
also found that if you set one Coordinator and one Datanode on the same
machine, Coordinator was using 30% of ressources and Datanode 70%.
With such numbers, a ratio of 0.5 is also possible.

>
>
>>
>> 2. Configuration :  What should be the differences between
>> postgresql.conf in /datanode and /coordinator, if there are any?
>
> Coordinator uses a connection pooler process. So it needs to know the
following parameters:
coordinator_hosts, data_nodes_hosts, coordinator_ports, datanode_ports,
pooler_port, data_node_num, coord_num, pgxc_node_id, gtm_port, gtm_host,
datanode_user, datanode_passd, coord_passwd, coord_user.
You have also pooler connection parameters to set but I forgot all the
names.
For datanode, you have to take care of GTM connection parameter and
pgxc_node_id (used to register on GTM).

In your cluster you can have a Coordinator 1 and a Datanode 1 as the
difference between node type is made when registering nodes on GTM.


>
>> Some
>> portions are they ignored for a specific function (ex : coordinator vs
>> datanode config, etc...)
>> In this can pg_hba.conf & postgresql.conf be shared for the same
>> server (maybe using symbolic links...)
>>
> No, you have to set up each postgresql.conf and pg_hba.conf for each node
separately as each Coordinator and Datanode use different data folder.

>
>
>> 3. GTM : I get on second node an "WARNING:  Do not have a GTM snapshot
>> available", can this be related to previous config files/setup  ?
>>
> This error means that you didn't set up GTM connection parameters
correctly.

>
>
>>
>> 4. Administration : are there ways of getting the online status of the
>> nodes from one node to another
>>
>
> This is currently under development. I can provide you details later.
>
Those experimental functionalities are located on a separate branch called
ha_support in the GIT repo.

We are also thinking about adding some catalog extensions to allow
coordinator to keep an eye on Datanodes as such a view process is linker to
the connection pooling process.
This is just a thought though.
Now as we are focusing on code stability for the core, this is not a high
priority.
But as we merged with PostgreSQL 9.0, it may be possible in a close future
to use XC with HOT Standby nodes. Current streaming replication is not
synchronized so its usage is now limited in current XC.

If you have any other questions, don't hesitate.
Regards,
-- 
Michael Paquier
http://michaelpq.users.sourceforge.net

On Fri, Mar 4, 2011 at 8:06 PM, Lionel Frachon <lio...@gm...>wrote:

> Hello,
>
> I'm starting an evaluation of the cluster (not having any PG
> background, but Oracle & MySql for years...), and some questions
> appear to me after reading the doc, any help appreciated.
>

Thank you, I would suggest playing around with plain PG first. That would
help you a lot.


>
> My actual setup is :
> pgxc1 for GTM, Coordinator and datanode
> pgxc2 for datanode only
>

You mean you will have 2 computers, one will run GTM, Coordinator and 1st
datanode and the other the 2nd data node. If yes then this would be fine.

BTW what Linux distribution will you be using?

Please remember that for the first time gtm has to be started with -x option
and it is better to start gtm before you initdb for the coordinator and the
2 data nodes. For successive runs you should skip -x option. As a general
rule you should always start gtm first then the data nodes and then
the coordinator.


> 1.General : Is a coordinator needed for each node, or one coordinator
> 'to rule them all' can be setup ?
>

Yes, one coordinator serve multiple data nodes.


>
> 2. Configuration :  What should be the differences between
> postgresql.conf in /datanode and /coordinator, if there are any ?


Yes each node in the cluster has to have a unique node ID, that is picked
from the postgresql.conf.
The coordinator needs to know the number of data nodes, and info required to
to connect to them e.g. user name password etc
Other than that I don't remember any thing on top of my head.
Please take a look at the portions in the conf file specific to the XC, that
would help.


> Some
> portions are they ignored for a specific function (ex : coordinator vs
> datanode config, etc...)
> In this can pg_hba.conf & postgresql.conf be shared for the same
> server (maybe using symbolic links...)
>

No, as I explained earlier.


>
> 3. GTM : I get on second node an "WARNING:  Do not have a GTM snapshot
> available", can this be related to previous config files/setup  ?
>

For the first data node the default configuration of a localhost GTM would
be fine but for the 2nd data node you need to tell the data node where GTM
is located, for this you need to change the gtm_host parameter in the
postgresql.conf file of the 2nd datanode to the IP addeess of your first
computer (which runs GTM).


>
> 4. Administration : are there ways of getting the online status of the
> nodes from one node to another
>

This is currently under development. I can provide you details later.


>
> Thanks
>
> Lionel F.
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>

Hello,

I'm starting an evaluation of the cluster (not having any PG
background, but Oracle & MySql for years...), and some questions
appear to me after reading the doc, any help appreciated.

My actual setup is :
pgxc1 for GTM, Coordinator and datanode
pgxc2 for datanode only

1.General : Is a coordinator needed for each node, or one coordinator
'to rule them all' can be setup ?

2. Configuration :  What should be the differences between
postgresql.conf in /datanode and /coordinator, if there are any ? Some
portions are they ignored for a specific function (ex : coordinator vs
datanode config, etc...)
In this can pg_hba.conf & postgresql.conf be shared for the same
server (maybe using symbolic links...)

3. GTM : I get on second node an "WARNING:  Do not have a GTM snapshot
available", can this be related to previous config files/setup  ?

4. Administration : are there ways of getting the online status of the
nodes from one node to another

Thanks

Lionel F.

Hi all,

I have a couple of comments about the commit
d73ae5182149b08e0728edb96eee339e0c0498b7 (Mirroring and XCM support).
There are a couple of information that is not written in the commit message
so as not to make it too long.
Mirroring supports:
- SELECT queries
- DML queries
- DDL
- Multi INSERT
- EXECUTE DIRECT has been modified to be able to target directly mirrors.
- Cursor fetch

For instance,
EXECUTE DIRECT on node 1/2 'select * from foo';
will send the query directly to datanode 1, mirror 2.
The only addition consists of the format datanode_id/mirror_id when parsing
the query string.

There are still a couple of issues with this feature:
- Row count for DML is not correct (bug 3185566)
- CURRENT OF is not supported yet.
Those issues would need a better way to index datanode numbers than the one
used now,
more or less the same way that is used for EXECUTE DIRECT based on
PGXCMirror nodes.

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

Postgres-XC does not support yet serial tables (sequence created at the same
time as a table).
This has been reported by bug 3110406.
https://sourceforge.net/tracker/?func=detail&aid=3110406&group_id=311227&atid=1310232


On Thu, Jan 6, 2011 at 6:11 AM, Marcin Krol <mr...@gm...> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello everyone,
>
> I have successfully (?) configured XC on two nodes (the cluster
> successfully created database and role and granted privileges on the
> db), however I have encountered a problem:
>
> postgres=# \c etest;
> psql (8.4.3)
> You are now connected to database "etest".
> etest=# CREATE TABLE "user" (
> etest(#         id SERIAL NOT NULL,
> etest(#         name VARCHAR,
> etest(#         fullname VARCHAR,
> etest(#         srv1 VARCHAR,
> etest(#         srv2 VARCHAR,
> etest(#         PRIMARY KEY (id)
> etest(# )
> etest-# ;
> NOTICE:  CREATE TABLE will create implicit sequence "user_id_seq" for
> serial column "user.id"
> server closed the connection unexpectedly
>        This probably means the server terminated abnormally
>        before or while processing the request.
> The connection to the server was lost. Attempting reset: Succeeded.
>
> The SQL code is simple enough I thought?
>
> The snag is I'm using ORM (SQLAlchemy 0.6.5) and this is what generated
> that code.
>
> After restart of a cluster I'm getting:
>
> postgres=# \c etest
> psql (8.4.3)
> You are now connected to database "etest".
> etest=# create table "testme" (id INTEGER, name VARCHAR);
> ERROR:  Could not commit (or autocommit) data node connection
>
>
>
> - --
>
> Regards,
> mk
>
> - --
> Premature optimization is the root of all fun.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJNJN5+AAoJEFMgHzhQQ7hOEsQH/2VaXQovjZhR6IT085Jim1Gb
> RM3B5UMZ/rWfRaqDRUdtY3SaV5HDNQd+vtsCoHg71ftAFjutAlUC6JNB4hlypxiR
> MFvRO1nsCq3arQWEALxtbL4plHeHN28b1uJesB1vchjYJCvyR9MIIVSBU2P0Rnv+
> qutNm/0rhbDhCo+7xOmK3J0r9VdBKvA+9NgYAi9AH9m7sMbIAvMcABZ9ws8QMSeG
> /aOCeWYSQCmUtG8/YPcQxdruKC7+G/d0lgY+BK2jP4iu0wnWSYA4ihzBI+FuKq8t
> ZAOvN2ku6DNvVGSeEnesOL9uK0dUOK1nkENmAd1AMMQ81jHcFB9hADrO/7oO530=
> =4/r3
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment,
> and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>



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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello everyone,

I wrote (mostly quick and dirty) script for generating XC config files,
distributing them to nodes and GTM, and starting and stopping cluster:

http://inet.btw2.pl/gen_pgxc_conf.tar.gz

I would appreciate if smbdy of you takes a look if generated files are OK...


- --

Regards,
mk

- --
Premature optimization is the root of all fun.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNJN83AAoJEFMgHzhQQ7hOuy8H/iP0SEVoIMtkwtH8kllU5N1v
s0JNu2LtSoUZeeFNR0tcJp2t1kbt/DkQgGIwGtPgwXFTEoc8aO7Mj/1aCpxWrxAZ
EuKCFrBfFKVSDaZxaHHuIEXHEwikXtTDH5qHG4776J60hXv9tUM29TWUh/cGDfvC
AE+uoQNX134r6I/z3JUGOMZzk7fvxgJuhyoL2e6xzJPgW1BPwXooGz7CRrIKl8Xt
at7cMnTcI3XV4BQuCYhrbSX/ckhrclapZe1lngrZRmR5Um50WsoZSJ/VhVAgLBRu
t1s0zi8nY4OqDQwg+2uXGRjA524oDK4g8RCKox2XQuqZj1ioQi4Mbx+rk1rWk2w=
=ugXX
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello everyone,

I have successfully (?) configured XC on two nodes (the cluster
successfully created database and role and granted privileges on the
db), however I have encountered a problem:

postgres=# \c etest;
psql (8.4.3)
You are now connected to database "etest".
etest=# CREATE TABLE "user" (
etest(#         id SERIAL NOT NULL,
etest(#         name VARCHAR,
etest(#         fullname VARCHAR,
etest(#         srv1 VARCHAR,
etest(#         srv2 VARCHAR,
etest(#         PRIMARY KEY (id)
etest(# )
etest-# ;
NOTICE:  CREATE TABLE will create implicit sequence "user_id_seq" for
serial column "user.id"
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.

The SQL code is simple enough I thought?

The snag is I'm using ORM (SQLAlchemy 0.6.5) and this is what generated
that code.

After restart of a cluster I'm getting:

postgres=# \c etest
psql (8.4.3)
You are now connected to database "etest".
etest=# create table "testme" (id INTEGER, name VARCHAR);
ERROR:  Could not commit (or autocommit) data node connection



- --

Regards,
mk

- --
Premature optimization is the root of all fun.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNJN5+AAoJEFMgHzhQQ7hOEsQH/2VaXQovjZhR6IT085Jim1Gb
RM3B5UMZ/rWfRaqDRUdtY3SaV5HDNQd+vtsCoHg71ftAFjutAlUC6JNB4hlypxiR
MFvRO1nsCq3arQWEALxtbL4plHeHN28b1uJesB1vchjYJCvyR9MIIVSBU2P0Rnv+
qutNm/0rhbDhCo+7xOmK3J0r9VdBKvA+9NgYAi9AH9m7sMbIAvMcABZ9ws8QMSeG
/aOCeWYSQCmUtG8/YPcQxdruKC7+G/d0lgY+BK2jP4iu0wnWSYA4ihzBI+FuKq8t
ZAOvN2ku6DNvVGSeEnesOL9uK0dUOK1nkENmAd1AMMQ81jHcFB9hADrO/7oO530=
=4/r3
-----END PGP SIGNATURE-----