postgres-xc-general Mailing List for Postgres-XC

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.