postgres-xc-developers Mailing List for Postgres-XC

Hi,
Attached please find patch to avoid the following XC limitation while
running JDBC regression
ERROR: Cannot create index whose evaluation cannot be enforced to remote
nodes

The solution was to replicate the tables on which indexes are being created.

-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

Hi Afonso,


> Afonso,
> Is this newly created device? My wild guess is, the server was not fully
> recovered (after some crash may be), and thus put in read only mode.
>
> OR
> for some reason, default transaction mode is read-only.
>
> We need more context.
>
>
>
Please check if the coordinator was started as a datanode by mistake!

Regards,
Nikhils



> On Fri, Jul 26, 2013 at 8:20 PM, Afonso Bione <aag...@gm...> wrote:
>
>> Dear Friend,
>> I installed the newest version of postgres xc and when I create a
>> database I get the error message "-bash-4.1 $ createdb moodle4
>> ERROR: CREATE DATABASE can not run in a read-only transaction
>> STATEMENT: CREATE DATABASE moodle4;
>>
>> *createdb*: database creation failed: ERROR: CREATE DATABASE can not run in
>> a read-only transaction "
>> My settings are:
>> 13567? Ps 12:22 GTM-D / var / lib / pgsql / data_gtm
>> 22159 pts / 0 S + 0:00 grep gtm
>> 28265? Ps 00:00 / var / lib / pgsql / bin / gtm_proxy-D / var / lib /
>> pgsql / gtm_proxy-l logfile
>>
>> the* gtm.conf*
>> nodename = 'one' # Specifies the node name.
>>                                          # (Changes requires restart)
>> listen_addresses = '*' # Listen addresses of this GTM.
>>                                          # (Changes requires restart)
>> port = 6666 # Port number of this GTM.
>>                                          # (Changes requires restart)
>>
>> ACT = # startup # Start mode. ACT / STANDBY.
>>
>> my *gtm_proxy.conf*
>>
>> nodename = 'one'                                        # Specifies the
>> node name.
>>                                                                 #
>> (changes requires restart)
>> listen_addresses = '*'                  # Listen addresses of this GTM.
>>                                                                 #
>> (changes requires restart)
>> port = 20008                            # Port number of this GTM.
>>                                                                 #
>> (changes requires restart)
>>
>>
>>
>> the *datanode*:
>> postgres --datanode -i -D /var/lib/pgsql/data
>>
>> the *postgresql.conf*
>> gtm_host = 'localhost'                  # Host name or address of GTM
>>                                         # (change requires restart)
>> gtm_port = 6666                 # Port of GTM
>>                                         # (change requires restart)
>> pgxc_node_name = 'one'                  # Coordinator or Datanode name
>>                                         # (change requires restart)
>>
>> Best regards
>>
>> thanks
>> Afonso Bione
>>
>>
>
>
> --
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Postgres Database Company
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>


-- 
StormDB - http://www.stormdb.com
The Database Cloud

Including hackers,

Afonso,
Is this newly created device? My wild guess is, the server was not fully
recovered (after some crash may be), and thus put in read only mode.

OR
for some reason, default transaction mode is read-only.

We need more context.


On Fri, Jul 26, 2013 at 8:20 PM, Afonso Bione <aag...@gm...> wrote:

> Dear Friend,
> I installed the newest version of postgres xc and when I create a database I
> get the error message "-bash-4.1 $ createdb moodle4
> ERROR: CREATE DATABASE can not run in a read-only transaction
> STATEMENT: CREATE DATABASE moodle4;
>
> *createdb*: database creation failed: ERROR: CREATE DATABASE can not run in
> a read-only transaction "
> My settings are:
> 13567? Ps 12:22 GTM-D / var / lib / pgsql / data_gtm
> 22159 pts / 0 S + 0:00 grep gtm
> 28265? Ps 00:00 / var / lib / pgsql / bin / gtm_proxy-D / var / lib /
> pgsql / gtm_proxy-l logfile
>
> the* gtm.conf*
> nodename = 'one' # Specifies the node name.
>                                          # (Changes requires restart)
> listen_addresses = '*' # Listen addresses of this GTM.
>                                          # (Changes requires restart)
> port = 6666 # Port number of this GTM.
>                                          # (Changes requires restart)
>
> ACT = # startup # Start mode. ACT / STANDBY.
>
> my *gtm_proxy.conf*
>
> nodename = 'one'                                        # Specifies the
> node name.
>                                                                 # (changes
> requires restart)
> listen_addresses = '*'                  # Listen addresses of this GTM.
>                                                                 # (changes
> requires restart)
> port = 20008                            # Port number of this GTM.
>                                                                 # (changes
> requires restart)
>
>
>
> the *datanode*:
> postgres --datanode -i -D /var/lib/pgsql/data
>
> the *postgresql.conf*
> gtm_host = 'localhost'                  # Host name or address of GTM
>                                         # (change requires restart)
> gtm_port = 6666                 # Port of GTM
>                                         # (change requires restart)
> pgxc_node_name = 'one'                  # Coordinator or Datanode name
>                                         # (change requires restart)
>
> Best regards
>
> thanks
> Afonso Bione
>
>


-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Postgres Database Company

Thank you Stephan for the patch.

I have noticed this and the patch was committed both to the master and REL1_1_STABLE.
---
Koichi Suzuki



On 2013/07/26, at 23:18, "Himpich, Stefan" <Ste...@se...> wrote:

> There is a "}" too many which causes the configs for datanodes to be wrong. Please include the following patch.
> 
> Greetings,
> Stefan
> 
> --- datanode_cmd.c.orig	2013-07-24 12:09:24.000000000 +0200
> +++ datanode_cmd.c	2013-07-26 16:16:01.234469379 +0200
> @@ -136,7 +136,7 @@
> 		fprintf(f,
> 				"wal_level = hot_standby\n"
> 				"archive_mode = on\n"
> -				"archive_command = 'rsync %%p %s@%s}:%s/%%f'\n"
> +				"archive_command = 'rsync %%p %s@%s:%s/%%f'\n"
> 				"max_wal_senders = %s\n"
> 				"# End of Addition\n",
> 				sval(VAR_pgxcUser), aval(VAR_datanodeSlaveServers)[idx], aval(VAR_datanodeArchLogDirs)[idx],
> 
> 
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> 

There is a "}" too many which causes the configs for datanodes to be wrong. Please include the following patch.

Greetings,
Stefan

--- datanode_cmd.c.orig	2013-07-24 12:09:24.000000000 +0200
+++ datanode_cmd.c	2013-07-26 16:16:01.234469379 +0200
@@ -136,7 +136,7 @@
 		fprintf(f,
 				"wal_level = hot_standby\n"
 				"archive_mode = on\n"
-				"archive_command = 'rsync %%p %s@%s}:%s/%%f'\n"
+				"archive_command = 'rsync %%p %s@%s:%s/%%f'\n"
 				"max_wal_senders = %s\n"
 				"# End of Addition\n",
 				sval(VAR_pgxcUser), aval(VAR_datanodeSlaveServers)[idx], aval(VAR_datanodeArchLogDirs)[idx],

Hi,
In order to avoid the limitation that partition column cannot be updated I
changed table distribution to round robin.
The patch is attached.

-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

Updated patch to add a space before DISTRIBUTE BY clause.

On Fri, Jul 26, 2013 at 4:33 PM, Abbas Butt <abb...@en...>wrote:

> Updated patch to support the DISTRIBUTE BY clause while creating temp
> tables too.
>
>
> On Fri, Jul 26, 2013 at 12:53 PM, Abbas Butt <abb...@en...>wrote:
>
>> Hi,
>> PFA patch that adds support to specify the optional DISTRIBUTE BY clause
>> while creating a table in JDBC test suite.
>> An existing function in the test suite has been modified and a new
>> function was added. This function will be used in the subsequent patches.
>>
>> --
>> *Abbas*
>>  Architect
>>
>> Ph: 92.334.5100153
>>  Skype ID: gabbasb
>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>> *
>> Follow us on Twitter*
>> @EnterpriseDB
>>
>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>
>
>
>
> --
> --
> *Abbas*
>  Architect
>
> Ph: 92.334.5100153
>  Skype ID: gabbasb
> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
> *
> Follow us on Twitter*
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>



-- 
-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

Updated patch to support the DISTRIBUTE BY clause while creating temp
tables too.

On Fri, Jul 26, 2013 at 12:53 PM, Abbas Butt <abb...@en...>wrote:

> Hi,
> PFA patch that adds support to specify the optional DISTRIBUTE BY clause
> while creating a table in JDBC test suite.
> An existing function in the test suite has been modified and a new
> function was added. This function will be used in the subsequent patches.
>
> --
> *Abbas*
>  Architect
>
> Ph: 92.334.5100153
>  Skype ID: gabbasb
> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
> *
> Follow us on Twitter*
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>



-- 
-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

Hi,
PFA patch that adds support to specify the optional DISTRIBUTE BY clause
while creating a table in JDBC test suite.
An existing function in the test suite has been modified and a new function
was added. This function will be used in the subsequent patches.

-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

Hi,
Currently XC cannot prepare a transaction if it has operated on temp
tables. It gives the following error in such a case

    [junit] ERROR: cannot PREPARE a transaction that has operated on
temporary tables
    [junit]   Detail: Disabling enforce_two_phase_commit is recommended to
enforce COMMIT

The attached patch fixes this error every where in the test suite by
setting enforce_two_phase_commit to false.

-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

Please configure gtm_proxy at DB01, DB02, dbback01 and dbback02.  The reasons are:

1. gtm_proxy groups up traffic between GTM and coordinator/datanode backgrounds.   Placing gtm_proxy at GTM2 will not benefit this.   Pgxc_ctl looks for a gtm_proxy local to coordinator/datanode.   Your configuration will make gtm_proxy available.

2. When you failover a datanode, in pgxc_ctl, a slave will look for a local gtm_proxy, otherwise the slave will be connected directly to gtm.   You need to configure gtm_proxy local to dbback01 and dbback02.

Hope this helps.

Regards;
---
Koichi Suzuki



On 2013/07/25, at 2:15, "Himpich, Stefan" <Ste...@se...> wrote:

> Hi there!
> 
> My current setup consists of 6 Servers:
> 
> GTM1
> - with gtm master
> 
> GTM2
> - with gtm standby
> - with gtm_proxy
> 
> DB01
> - with coordinator1 (master)
> - with datanode1 (master)
> 
> DB02
> - with coordinator2 (master)
> - with datanode2 (master)
> 
> dbback01 
> - with datanode2_slave
> 
> dbback02
> - with datanode1_slave
> 
> 
> Setup using pgxc_ctl init all works fine.
> 
> I simulate a servercrash by shutting down:
> GTM2
> DB02
> dbback02
> 
> Then (via pgxc_ctl) I remove:
> gtm slave
> gtm_proxy
> datanode2
> datanode1_slave
> 
> Unfortunatly, this does not work if a gtm slave is envolved. The GTM still thinks there should be a gtm standby and times out trying to contact it.
> 
> 1:140702615140096:2013-07-24 19:00:01.841 UTC -LOG:  Failed to establish a connection with GTM standby. - 0x1dfd918
> LOCATION:  gtm_standby_connect_to_standby_int, gtm_standby.c:396
> 1:140702615140096:2013-07-24 19:00:55.893 UTC -LOG:  Failed to establish a connection with GTM standby. - 0x1dfd918
> LOCATION:  gtm_standby_connect_to_standby_int, gtm_standby.c:396
> 1:140702615140096:2013-07-24 19:00:58.893 UTC -LOG:  Failed to establish a connection with GTM standby. - 0x1dfd918
> LOCATION:  gtm_standby_connect_to_standby_int, gtm_standby.c:396
> 1:140702615140096:2013-07-24 19:01:01.893 UTC -LOG:  Failed to establish a connection with GTM standby. - 0x1dfd918
> LOCATION:  gtm_standby_connect_to_standby_int, gtm_standby.c:396
> 
> 
> 
> monitor all output when everything was fine:
> pgxc_ctl(32409):1307241419_00 PGXC monitor all
> pgxc_ctl(32409):1307241419_00 Running: gtm master
> pgxc_ctl(32409):1307241419_00 Running: gtm slave
> pgxc_ctl(32409):1307241419_00 Running: gtm proxy gtm97-proxy
> pgxc_ctl(32409):1307241419_00 Running: coordinator master coorddbms181
> pgxc_ctl(32409):1307241419_00 Running: coordinator master coorddbms197
> pgxc_ctl(32409):1307241419_00 Running: datanode master datadbms181
> pgxc_ctl(32409):1307241419_00 Running: datanode slave datadbms181
> pgxc_ctl(32409):1307241419_00 Running: datanode master datadbms197
> pgxc_ctl(32409):1307241419_00 Running: datanode slave datadbms197
> 
> 
> monitor all output after (intentional) crash of server*2:
> pgxc_ctl(32409):1307241436_36 PGXC monitor all
> pgxc_ctl(32409):1307241437_35 Running: gtm master
> pgxc_ctl(32409):1307241437_38 Not running: gtm slave
> pgxc_ctl(32409):1307241437_41 Not running: gtm proxy gtm97-proxy
> pgxc_ctl(32409):1307241437_41 Running: coordinator master coorddbms181
> pgxc_ctl(32409):1307241437_59 Not running: coordinator master coorddbms197
> pgxc_ctl(32409):1307241437_59 Running: datanode master datadbms181
> pgxc_ctl(32409):1307241438_17 Not running: datanode slave datadbms181
> pgxc_ctl(32409):1307241438_20 Not running: datanode master datadbms197
> pgxc_ctl(32409):1307241438_20 Running: datanode slave datadbms197
> 
> removal of gtm slave:
> pgxc_ctl(32409):1307241500_38 PGXC remove gtm slave
> pgxc_ctl(32409):1307241500_41 Removing gtm slave.
> pgxc_ctl(32409):1307241500_41 Done.
> 
> 
> [removal of remaining "not runing" parts, failover of slave datenode, etc]
> 
> pgxc_ctl(32409):1307241540_40 PGXC monitor all
> pgxc_ctl(32409):1307241540_42 Running: gtm master
> pgxc_ctl(32409):1307241540_42 Running: coordinator master coorddbms181
> pgxc_ctl(32409):1307241540_42 Running: datanode master datadbms181
> pgxc_ctl(32409):1307241540_42 Running: datanode master datadbms197
> 
> 
> But - as seen above - the gtm master still thinks he has a slave and tries (forever) to contact it.
> Restart of the whole (remaining) cluster doesn't help, too.
> 
> 
> 
> The same setup without a gtm slave works fine - but I need it in case 'server*1' crashes.
> 
> Any thoughts on that topic, any logging I might supply?
> 
> Regards,
> Stefan
> 
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> 

PFA a revised patch in which I have done the following change.
Instead of creating the flag variable to indicate that the tests are being
run for XC in Driver.java.in, I have created a function in TestUtil.java
that returns the state of the property created in build.xml.
This is to make sure that the changes are restricted to the test suite only.
Thanks Masataka for reviewing the patch.


On Wed, Jul 24, 2013 at 12:06 PM, Abbas Butt <abb...@en...>wrote:

>
>
> On Wed, Jul 24, 2013 at 10:09 AM, Michael Paquier <
> mic...@gm...> wrote:
>
>>
>>
>>
>> On Wed, Jul 24, 2013 at 2:00 PM, Ashutosh Bapat <
>> ash...@en...> wrote:
>>
>>> For the sake of everyone's understanding, it would be nice if you can
>>> describe the general structure of JDBC testcases (if there is write-up
>>> available point to it) and description of specific problems. E.g. what is
>>> this build.xml, what does it do? What is the particular problem and so on.
>>>
>> +1. Why is this patch for jdbc here?
>>
>
> The patch is not for JDBC, it is for JDBC Regression. Our intention is to
> run JDBC regression against XC, and we need to change a few things in the
> test suite to run it like I have mentioned in my previous email in this
> chain.
>
>
>> Are you guys planning to fork jdbc for XC?
>>
>
> No.
>
>
>>  I am still not able to read in people's mind, especially when they are a
>> couple of thousand kilometers far, so any clarification would be good.
>>
>
> We intend to send small patches so that the review is easy and then
> combine them all to make a single patch that would be required to be
> applied to PG JDBC regression suite before it runs against XC with minimal
> failures.
>
>
>
>> --
>> Michael
>>
>
>
>
> --
> --
> *Abbas*
>  Architect
>
> Ph: 92.334.5100153
>  Skype ID: gabbasb
> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
> *
> Follow us on Twitter*
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>



-- 
-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

Hi there!

My current setup consists of 6 Servers:

GTM1
- with gtm master

GTM2
- with gtm standby
- with gtm_proxy

DB01
- with coordinator1 (master)
- with datanode1 (master)

DB02
- with coordinator2 (master)
- with datanode2 (master)

dbback01 
- with datanode2_slave

dbback02
- with datanode1_slave


Setup using pgxc_ctl init all works fine.

I simulate a servercrash by shutting down:
GTM2
DB02
dbback02

Then (via pgxc_ctl) I remove:
gtm slave
gtm_proxy
datanode2
datanode1_slave

Unfortunatly, this does not work if a gtm slave is envolved. The GTM still thinks there should be a gtm standby and times out trying to contact it.

1:140702615140096:2013-07-24 19:00:01.841 UTC -LOG:  Failed to establish a connection with GTM standby. - 0x1dfd918
LOCATION:  gtm_standby_connect_to_standby_int, gtm_standby.c:396
1:140702615140096:2013-07-24 19:00:55.893 UTC -LOG:  Failed to establish a connection with GTM standby. - 0x1dfd918
LOCATION:  gtm_standby_connect_to_standby_int, gtm_standby.c:396
1:140702615140096:2013-07-24 19:00:58.893 UTC -LOG:  Failed to establish a connection with GTM standby. - 0x1dfd918
LOCATION:  gtm_standby_connect_to_standby_int, gtm_standby.c:396
1:140702615140096:2013-07-24 19:01:01.893 UTC -LOG:  Failed to establish a connection with GTM standby. - 0x1dfd918
LOCATION:  gtm_standby_connect_to_standby_int, gtm_standby.c:396



monitor all output when everything was fine:
pgxc_ctl(32409):1307241419_00 PGXC monitor all
pgxc_ctl(32409):1307241419_00 Running: gtm master
pgxc_ctl(32409):1307241419_00 Running: gtm slave
pgxc_ctl(32409):1307241419_00 Running: gtm proxy gtm97-proxy
pgxc_ctl(32409):1307241419_00 Running: coordinator master coorddbms181
pgxc_ctl(32409):1307241419_00 Running: coordinator master coorddbms197
pgxc_ctl(32409):1307241419_00 Running: datanode master datadbms181
pgxc_ctl(32409):1307241419_00 Running: datanode slave datadbms181
pgxc_ctl(32409):1307241419_00 Running: datanode master datadbms197
pgxc_ctl(32409):1307241419_00 Running: datanode slave datadbms197


monitor all output after (intentional) crash of server*2:
pgxc_ctl(32409):1307241436_36 PGXC monitor all
pgxc_ctl(32409):1307241437_35 Running: gtm master
pgxc_ctl(32409):1307241437_38 Not running: gtm slave
pgxc_ctl(32409):1307241437_41 Not running: gtm proxy gtm97-proxy
pgxc_ctl(32409):1307241437_41 Running: coordinator master coorddbms181
pgxc_ctl(32409):1307241437_59 Not running: coordinator master coorddbms197
pgxc_ctl(32409):1307241437_59 Running: datanode master datadbms181
pgxc_ctl(32409):1307241438_17 Not running: datanode slave datadbms181
pgxc_ctl(32409):1307241438_20 Not running: datanode master datadbms197
pgxc_ctl(32409):1307241438_20 Running: datanode slave datadbms197

removal of gtm slave:
pgxc_ctl(32409):1307241500_38 PGXC remove gtm slave
pgxc_ctl(32409):1307241500_41 Removing gtm slave.
pgxc_ctl(32409):1307241500_41 Done.


[removal of remaining "not runing" parts, failover of slave datenode, etc]

pgxc_ctl(32409):1307241540_40 PGXC monitor all
pgxc_ctl(32409):1307241540_42 Running: gtm master
pgxc_ctl(32409):1307241540_42 Running: coordinator master coorddbms181
pgxc_ctl(32409):1307241540_42 Running: datanode master datadbms181
pgxc_ctl(32409):1307241540_42 Running: datanode master datadbms197


But - as seen above - the gtm master still thinks he has a slave and tries (forever) to contact it.
Restart of the whole (remaining) cluster doesn't help, too.



The same setup without a gtm slave works fine - but I need it in case 'server*1' crashes.

Any thoughts on that topic, any logging I might supply?

Regards,
Stefan

Hi,
PFA patch to support creation of temporary tables through JDBC test suite.

-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

On Wed, Jul 24, 2013 at 10:09 AM, Michael Paquier <mic...@gm...
> wrote:

>
>
>
> On Wed, Jul 24, 2013 at 2:00 PM, Ashutosh Bapat <
> ash...@en...> wrote:
>
>> For the sake of everyone's understanding, it would be nice if you can
>> describe the general structure of JDBC testcases (if there is write-up
>> available point to it) and description of specific problems. E.g. what is
>> this build.xml, what does it do? What is the particular problem and so on.
>>
> +1. Why is this patch for jdbc here?
>

The patch is not for JDBC, it is for JDBC Regression. Our intention is to
run JDBC regression against XC, and we need to change a few things in the
test suite to run it like I have mentioned in my previous email in this
chain.


> Are you guys planning to fork jdbc for XC?
>

No.


> I am still not able to read in people's mind, especially when they are a
> couple of thousand kilometers far, so any clarification would be good.
>

We intend to send small patches so that the review is easy and then combine
them all to make a single patch that would be required to be applied to PG
JDBC regression suite before it runs against XC with minimal failures.



> --
> Michael
>



-- 
-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

On Wed, Jul 24, 2013 at 10:00 AM, Ashutosh Bapat <
ash...@en...> wrote:

> For the sake of everyone's understanding, it would be nice if you can
> describe the general structure of JDBC testcases (if there is write-up
> available point to it) and description of specific problems. E.g. what is
> this build.xml, what does it do? What is the particular problem and so on.
>

For the general structure of the JDBC test cases please refer to the
following links

1. http://jdbc.postgresql.org/index.html
2. http://jdbc.postgresql.org/development/intro.html

When we try to run JDBC test suite against XC we face the following problems

1. XC does not support large objects & svaepoints, JDBC driver test suite
tests them.
2. XC needs enforce_two_phase_commit to be set to false to create temporary
tables.
   JDBC driver test suite creates temporary tables.
3. XC needs a DISTRIBUTE BY clause to be specified in case the user does
not want the default.
   JDBC driver test suite creates tables and then tries to update their
distribution column.
   We will need to change the distribution of these tables to REPLICATED,
in all cases where
   making such a change does not impact the test itself.
There will be other problems too, that we have not yet discovered.

I had already provided this info in my previous email with subject "JDBC
Regression" dated 13 june 2013.

build.xml is the default build file for Apache Ant.
JDBC test suite uses Ant which is a Java based build tool.
For more details please refer to the following link
http://ant.apache.org/manual/using.html

For the current patch the problem is that XC does not support large objects
and JDBC driver test suite tests large objects.
There is not such thing as original expected output file and there is no
concept of alternate expected output files
hence we decided to skip the test. To skip the test I have added a new
configuration parameter in build.xml and then
when the test suite was about to test support for large objects I checked
that if the configuration parameter is set
there is no need to perform this test.

To get an idea of how does JDBC driver perform tests, here is a sample test

1. Open a database connection

        con = TestUtil.openDB();

2. Create a statement

        st = con.createStatement();

3. Perform the operation

        // Now update image to 9876 and commit
        st.executeUpdate("update test_a set image=9876 where id=5678");
        con.commit();

4. Confirm the operation

        rs = st.executeQuery("select image from test_a where id=5678");
        assertTrue(rs.next());
        assertEquals(9876, rs.getInt(1));

5. Clean up

        rs.close();
        TestUtil.closeDB(con);


For a complete example please take a look at function testTransactions()
in file org/postgresql/test/jdbc2/ConnectionTest.java

To download the test suite along with the driver please use

git clone git://github.com/pgjdbc/pgjdbc.git

Regards



>
>
> On Wed, Jul 24, 2013 at 6:34 AM, Abbas Butt <abb...@en...>wrote:
>
>> Hi,
>> PFA the patch.
>> It adds another configuration parameter in build.xml to select whether
>> the tests are being run for XC.
>> If set the tests for unsupported features re skipped.
>>
>> Comments are welcome.
>>
>> --
>> *Abbas*
>>  Architect
>>
>> Ph: 92.334.5100153
>>  Skype ID: gabbasb
>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>> *
>> Follow us on Twitter*
>> @EnterpriseDB
>>
>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>>
>
>
> --
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Postgres Database Company
>



-- 
-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

On Wed, Jul 24, 2013 at 2:00 PM, Ashutosh Bapat <
ash...@en...> wrote:

> For the sake of everyone's understanding, it would be nice if you can
> describe the general structure of JDBC testcases (if there is write-up
> available point to it) and description of specific problems. E.g. what is
> this build.xml, what does it do? What is the particular problem and so on.
>
+1. Why is this patch for jdbc here? Are you guys planning to fork jdbc for
XC? I am still not able to read in people's mind, especially when they are
a couple of thousand kilometers far, so any clarification would be good.
-- 
Michael

For the sake of everyone's understanding, it would be nice if you can
describe the general structure of JDBC testcases (if there is write-up
available point to it) and description of specific problems. E.g. what is
this build.xml, what does it do? What is the particular problem and so on.


On Wed, Jul 24, 2013 at 6:34 AM, Abbas Butt <abb...@en...>wrote:

> Hi,
> PFA the patch.
> It adds another configuration parameter in build.xml to select whether the
> tests are being run for XC.
> If set the tests for unsupported features re skipped.
>
> Comments are welcome.
>
> --
> *Abbas*
>  Architect
>
> Ph: 92.334.5100153
>  Skype ID: gabbasb
> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
> *
> Follow us on Twitter*
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>


-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Postgres Database Company

Hi,
PFA the patch.
It adds another configuration parameter in build.xml to select whether the
tests are being run for XC.
If set the tests for unsupported features re skipped.

Comments are welcome.

-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

On Fri, Jul 19, 2013 at 12:15 PM, Ahsan Hadi <ahs...@en...>wrote:

> Hi Pavan,
>
> Can you review the patch from Ashutosh and see if that addresses the issue
> you have raised.
>
>
Looks good to me. Thanks.

Hi Abbas,

(2013/07/19 20:37), Abbas Butt wrote:
 > I had a look at your patch, here is my feedback.
 >
Thank you for the feedback.

 > 1. The problem you reported seems to be caused by a missing 
initialization
 > i.e.
 > query->rtable = NIL;
 > Can you please explain why did the server crash and how it got fixed by
 > having the above initialization statement?
The fix has nothing to do with server crash.
The test environment(2datanodes and 1cordinator) avoids the crash.

 > It would be nice to add some comment on top of this line explaining it.
 >
To be honest, I don't know why my fix solves
my infinite loop problem.
I'll check it deeper and revise the patch.
Please wait for it.

 > 2. I think your patch unintentionally includes a change in
 > contrib/pgxc_ctl/signature.h
 >     Can you please remove it?
 >
OK, I'll do it.

 > 3. Can you please add a test case in say xc_misc.sql?
 >
OK, I'll do it too.

regards,
-------------------
NTT Software Corporation
Tomonari Katsumata

> I am working on some case study, and wants to know which one is best for
> Hive Metastore PostgresSQL/Postgres-XC or MySQL. if any one is having any
> document, link or resource please give me the link.
>
>
>
Stock PostgreSQL should be good enough as a Hive metastore. Don't think XC
would be a good fit for it. No comments about the latter :)

Regards,
Nikhils


> --
> ViVek Raghuwanshi
> Mobile -+91-09595950504
> Skype - vivek_raghuwanshi
> IRC vivekraghuwanshi
> http://vivekraghuwanshi.wordpress.com/
> http://in.linkedin.com/in/vivekraghuwanshi
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>


-- 
StormDB - http://www.stormdb.com
The Database Cloud

Hi All,

I am not sure if this is a right mailing list in not please suggest/forward.

I am working on some case study, and wants to know which one is best for
Hive Metastore PostgresSQL/Postgres-XC or MySQL. if any one is having any
document, link or resource please give me the link.


-- 
ViVek Raghuwanshi
Mobile -+91-09595950504
Skype - vivek_raghuwanshi
IRC vivekraghuwanshi
http://vivekraghuwanshi.wordpress.com/
http://in.linkedin.com/in/vivekraghuwanshi

On Sat, Jul 20, 2013 at 11:50 PM, Tomasz Straszewski <
str...@gm...> wrote:

> Hi,
>
> I have a question about transactions, i readed that postgres-xc doesn't
> support savepoints. What happens if transaction fails ?
>
Same answer as on the other mailing list: All the modifications done by
this transaction are dropped on all the nodes involved as it rollbacks.
Thanks,
-- 
Michael

Hi,

I have a question about transactions, i readed that postgres-xc doesn't 
support savepoints. What happens if transaction fails ?

My application use postgreSQL and implement savepoint dao class with 
create savepoint in database. I want to migrate from postgreSQL to 
postgres-xc and i don't know what to do in this situation.

Regards