postgres-xc-developers — Postgres-XC hackers and developers

Re: [Postgres-xc-developers] [JDBC Regression] Fix for XC does not support serializable transactions

[Masataka S. <pg...@gm...>]

The patch will work fine.

But this is my basal question:
setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE) after XC
block doesn't raise an exception, I know.
Is it right shelving unsupported isolation level without an error?

On Fri, Aug 2, 2013 at 4:36 PM, Abbas Butt <abb...@en...> wrote:
> Hi,
> PFA patch to make sure that JDBC regression skips tests for serializable
> transactions.
>
> --
> Abbas
> Architect
>
> Ph: 92.334.5100153
> Skype ID: gabbasb
> www.enterprisedb.com
>
> Follow us on Twitter
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers and more
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>

Re: [Postgres-xc-developers] [JDBC Regression] XC does not support binary transfer of fields

[Masataka S. <pg...@gm...>]

On Mon, Aug 5, 2013 at 4:45 PM, Abbas Butt <abb...@en...> wrote:
>
>
> On Mon, Aug 5, 2013 at 10:22 AM, Masataka Saito <pg...@gm...> wrote:
>>
>> HI,
>>
>> It's OK If you know the property could be changed by
>> build.local.properties file and you daringly changed build.xml directly.
>
>
> I had opted to change build.xml instead of adding another file in the
> repository, but we can do it the way you are suggesting. I remember testing
> it and it was working fine. Should I send an updated patch that adds a file
> build.local.properties containing binarytransfer=false?

I just wanted to know whether you recognize options or not.
It is needless to fix.

>
>>
>>
>>
>> On Fri, Aug 2, 2013 at 4:33 PM, Abbas Butt <abb...@en...>
>> wrote:
>>>
>>> Hi,
>>> PFA patch to make sure that JDBC regression does not use binary transfer
>>> of fields since XC does not support it.
>>>
>>> --
>>> Abbas
>>> Architect
>>>
>>> Ph: 92.334.5100153
>>> Skype ID: gabbasb
>>> www.enterprisedb.com
>>>
>>> Follow us on Twitter
>>> @EnterpriseDB
>>>
>>> Visit EnterpriseDB for tutorials, webinars, whitepapers and more
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Get your SQL database under version control now!
>>> Version control is standard for application code, but databases havent
>>> caught up. So what steps can you take to put your SQL databases under
>>> version control? Why should you start doing it? Read more to find out.
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>
>>
>
>
>
> --
> --
> Abbas
> Architect
>
> Ph: 92.334.5100153
> Skype ID: gabbasb
> www.enterprisedb.com
>
> Follow us on Twitter
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers and more

Re: [Postgres-xc-developers] [JDBC Regression] Fix wrongly written boolean tests

[Masataka S. <pg...@gm...>]

Hi,

I feel feckless for sorting assertins.

I propose appending a serial column to test tables and SELECT rows
ORDERED BY it.
I think this idea makes costless and it doesn't against to the gist of the test.

Regards.

On Fri, Aug 2, 2013 at 8:47 PM, Abbas Butt <abb...@en...> wrote:
> Hi,
> PFA patch to fix wrongly written boolean tests, patch comments explain the
> errors and the fix.
>
> --
> Abbas
> Architect
>
> Ph: 92.334.5100153
> Skype ID: gabbasb
> www.enterprisedb.com
>
> Follow us on Twitter
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers and more
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>

Re: [Postgres-xc-developers] [JDBC Regression] XC does not support binary transfer of fields

[Abbas B. <abb...@en...>]

On Mon, Aug 5, 2013 at 10:22 AM, Masataka Saito <pg...@gm...> wrote:

> HI,
>
> It's OK If you know the property could be changed by
> build.local.properties file and you daringly changed build.xml directly.
>

I had opted to change build.xml instead of adding another file in the
repository, but we can do it the way you are suggesting. I remember testing
it and it was working fine. Should I send an updated patch that adds a file
build.local.properties containing binarytransfer=false?


>
>
> On Fri, Aug 2, 2013 at 4:33 PM, Abbas Butt <abb...@en...>wrote:
>
>> Hi,
>> PFA patch to make sure that JDBC regression does not use binary transfer
>> of fields since XC does not support it.
>>
>> --
>> *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>
>>
>>
>> ------------------------------------------------------------------------------
>> Get your SQL database under version control now!
>> Version control is standard for application code, but databases havent
>> caught up. So what steps can you take to put your SQL databases under
>> version control? Why should you start doing it? Read more to find out.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>>
>


-- 
-- 
*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>

Re: [Postgres-xc-developers] [JDBC Regression] Fix a spelling mistake

[Masataka S. <pg...@gm...>]

Hi,
I missed it. This patch is needed.


On Fri, Aug 2, 2013 at 4:35 PM, Abbas Butt <abb...@en...>wrote:

> Hi
> PFA patch to fix a spelling mistake.
>
> --
> *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>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>

Re: [Postgres-xc-developers] [JDBC Regression] XC does not support binary transfer of fields

[Masataka S. <pg...@gm...>]

HI,

It's OK If you know the property could be changed by build.local.properties
file and you daringly changed build.xml directly.


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

> Hi,
> PFA patch to make sure that JDBC regression does not use binary transfer
> of fields since XC does not support it.
>
> --
> *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>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>

[Postgres-xc-developers] Bad fraud under my name

[Koichi S. <koi...@gm...>]

Hello;

My e-mail account was hacked this morning and bad fraud message was sent to
some of my e-mail recipients.   It's asking your help to me.   Please
ignore it.

I regained control over my e-mail account and will change the account for
security.   Please allow me a couple of days for this.

Thank you very much;
----------
Koichi Suzuki

Re: [Postgres-xc-developers] Save Point

[Tomasz S. <str...@gm...>]

Hi,

Thanks for your response. I know that but alfresco doesn't have that 
capability...

Regards
Tomek

W dniu 2013-08-02 15:18, Nikhil Sontakke pisze:
> Typical systems have configuration parameters to enable/disable the 
> use of savepoints.
>
> Like in Django, AFAIR, it also uses savepoints by default, but then 
> you can turn if off via a configuration parameter.
>
> Regards,
> Nikhils
>
> On Fri, Aug 2, 2013 at 12:05 PM, Tomasz Straszewski 
> <str...@gm... <mailto:str...@gm...>> 
> wrote:
>
>     Hi,
>
>     I am working with alfresco system and i want postgresxc as
>     database to increase performence. Alfresco use funcionality "save
>     point" when is working with database and i don't want interfere in
>     source code because much modules and core use this funcionality.
>
>     Regards
>
>     W dniu 2013-08-02 03:36, 鈴木 幸市 pisze:
>>     Yes.
>>
>>     We had similar ML thread on this. Implementation will not be too
>>     tough so I'm curious about the use case and how serious it is.
>>
>>     Regards;
>>     ---
>>     Koichi Suzuki
>>
>>     On 2013/08/02, at 9:23, Michael Paquier
>>     <mic...@gm... <mailto:mic...@gm...>> wrote:
>>
>>>
>>>
>>>
>>>     On Thu, Aug 1, 2013 at 6:45 PM, Tomasz Straszewski
>>>     <str...@gm...
>>>     <mailto:str...@gm...>> wrote:
>>>
>>>         Is there chance to create "save point" functionality?. Now
>>>         this is very
>>>         important for me, because i can't use postgres xc without this
>>>         functionality.
>>>
>>>     It shouldn't be that hard to implement, just that this projects
>>>     lacks active developers (who perhaps themselves lack time...)
>>>     that could spend time on it. I recall that the priority for this
>>>     feature very not that high, but this can evolve based on demand.
>>>
>>>     Regards,
>>>     -- 
>>>     Michael
>>>     ------------------------------------------------------------------------------
>>>     Get your SQL database under version control now!
>>>     Version control is standard for application code, but databases
>>>     havent
>>>     caught up. So what steps can you take to put your SQL databases
>>>     under
>>>     version control? Why should you start doing it? Read more to
>>>     find out.
>>>     http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________
>>>     Postgres-xc-developers mailing list
>>>     Pos...@li...
>>>     <mailto:Pos...@li...>
>>>     https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>
>
>     ------------------------------------------------------------------------------
>     Get your SQL database under version control now!
>     Version control is standard for application code, but databases havent
>     caught up. So what steps can you take to put your SQL databases under
>     version control? Why should you start doing it? Read more to find out.
>     http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>     _______________________________________________
>     Postgres-xc-developers mailing list
>     Pos...@li...
>     <mailto:Pos...@li...>
>     https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>
>
>
> -- 
> StormDB - http://www.stormdb.com
> The Database Cloud 

Re: [Postgres-xc-developers] Minor Fixes

[Matt W. <MW...@XI...>]

Good morning.

I just wanted to check in and see whether there’s still an interest in the patches I submitted that allow XC to compile and run under Solaris with the Sun compiler.

Regards,

Matt

From: Koichi Suzuki [mailto:koi...@gm...]
Sent: Thursday, June 27, 2013 9:27 AM
To: Matt Warner
Cc: Postgres-XC Developers
Subject: Re: [Postgres-xc-developers] Minor Fixes

Thank you Matt.
Please wait a bit until branch for 1.1 is built.
Regards;

----------
Koichi Suzuki

2013/6/28 Matt Warner <MW...@xi...<mailto:MW...@xi...>>
I’d be happy to continue testing on Solaris.

From: Koichi Suzuki [mailto:koi...@gm...<mailto:koi...@gm...>]
Sent: Wednesday, June 26, 2013 11:19 PM
To: Matt Warner; Postgres-XC Developers

Subject: Re: [Postgres-xc-developers] Minor Fixes

Hi,
I reviewed this thread again.  It may be better to include Matt's patch to the master after we build REL1_1_STABLE so that he can continue his Solaris-related work on the master.   As Ashutosh suggested, it will be less confusing not to include this in REL1_1_STABLE.
Because I'm about to build REL1_1_STABLE for beta work, please let me know if anybody need Matt's patch in 1.1.
Matt, could you let me know your idea and if you can continue to test XC on Solaris and declare that XC supports Solaris?
Best Regards;

----------
Koichi Suzuki

2013/6/25 Koichi Suzuki <koi...@gm...<mailto:koi...@gm...>>
I meant that removing "return" statement which returns another function return value will be a good refactoring.   Of course, simple return may not be removed.


----------
Koichi Suzuki

2013/6/25 Koichi Suzuki <koi...@gm...<mailto:koi...@gm...>>
Year.   The code is not harmfull at all.    Removing "return" from void functions could be a good refactoring.   Although Solaris is not supported officieally yet, I think it's a good idea to have it in master.   I do hope Matt continues to test XC so that we can tell XC runs on Solaris.
Any more inputs?
Regardsds;

----------
Koichi Suzuki

2013/6/25 Matt Warner <MW...@xi...<mailto:MW...@xi...>>
I'll double check but I thought I'd only removed return from functions declaring void as their return type.

?

Matt

On Jun 23, 2013, at 6:22 PM, "鈴木 幸市" <ko...@in...<mailto:ko...@in...>> wrote:
The patch looks reasonable.   One comment: removing "return" for non-void function will cause Linux gcc warning.  For this case, we need #ifdef SOLARIS directive.

You sent two similar patch for proxy_main.c in separate e-mails.   The later one seems to resolve my comment above.   Although the core team cannot declare that XC runs on Solaris so far, I think the patch is reasonable to be included.

Any other comments?
---
Koichi Suzuki



On 2013/06/22, at 1:26, Matt Warner <MW...@XI...<mailto:MW...@XI...>> wrote:

Regarding the other changes, they are specific to Solaris. For example, in src/backend/pgxc/pool/pgxcnode.c, Solaris requires we include sys/filio.h. I’ll be searching to see if I can find a macro already defined for Solaris that I can leverage to #ifdef those Solaris-specific items.

Matt

From: Matt Warner
Sent: Friday, June 21, 2013 9:21 AM
To: 'Koichi Suzuki'
Cc: 'pos...@li...<mailto:pos...@li...>'
Subject: RE: [Postgres-xc-developers] Minor Fixes

First patch.

From: Matt Warner
Sent: Friday, June 21, 2013 8:50 AM
To: 'Koichi Suzuki'
Cc: pos...@li...<mailto:pos...@li...>
Subject: RE: [Postgres-xc-developers] Minor Fixes

Yes, I’m running XC on Solaris x64.

From: Koichi Suzuki [mailto:koi...@gm...]
Sent: Thursday, June 20, 2013 6:34 PM
To: Matt Warner
Cc: pos...@li...<mailto:pos...@li...>
Subject: Re: [Postgres-xc-developers] Minor Fixes

Thanks a lot for the patch.   As Michael mentioned, you can send a patch to developers mailing list.

BTW, core team tested current XC on 64bit Intel CentOS and others tested it against RedHat.    Did you test XC on Solaris?

Regards;

----------
Koichi Suzuki

2013/6/21 Matt Warner <MW...@xi...<mailto:MW...@xi...>>
Just a quick question about contributing fixes. I’ve had to make some minor changes to get XC compiled on Solaris x64.
What format would you like to see for the changes? Most are very minor, such as removing return statements inside void functions (which the Solaris compiler flags as incorrect since you can’t return from a void function).
Matt


------------------------------------------------------------------------------
This SF.net<http://SF.net> email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Postgres-xc-developers mailing list
Pos...@li...<mailto:Pos...@li...>
https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

------------------------------------------------------------------------------
This SF.net<http://SF.net> email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Postgres-xc-developers mailing list
Pos...@li...<mailto:Pos...@li...>
https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

Re: [Postgres-xc-developers] Save Point

[Nikhil S. <ni...@st...>]

Typical systems have configuration parameters to enable/disable the use of
savepoints.

Like in Django, AFAIR, it also uses savepoints by default, but then you can
turn if off via a configuration parameter.

Regards,
Nikhils

On Fri, Aug 2, 2013 at 12:05 PM, Tomasz Straszewski <
str...@gm...> wrote:

>  Hi,
>
> I am working with alfresco system and i want postgresxc as database to
> increase performence. Alfresco use funcionality "save point" when is
> working with database and i don't want interfere in source code because
> much modules and core use this funcionality.
>
> Regards
>
> W dniu 2013-08-02 03:36, 鈴木 幸市 pisze:
>
> Yes.
>
>  We had similar ML thread on this.   Implementation will not be too tough
> so I'm curious about the use case and how serious it is.
>
>  Regards;
> ---
> Koichi Suzuki
>
>  On 2013/08/02, at 9:23, Michael Paquier <mic...@gm...>
> wrote:
>
>
>
>
> On Thu, Aug 1, 2013 at 6:45 PM, Tomasz Straszewski <
> str...@gm...> wrote:
>
>> Is there chance to create "save point" functionality?. Now this is very
>> important for me, because i can't use postgres xc without this
>> functionality.
>>
> It shouldn't be that hard to implement, just that this projects lacks
> active developers (who perhaps themselves lack time...) that could spend
> time on it. I recall that the priority for this feature very not that high,
> but this can evolve based on demand.
>
>  Regards,
>  --
> Michael
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>
>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&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

[Postgres-xc-developers] GTM proxy log not showing debug messages?

[Nikhil S. <ni...@st...>]

Hi,

Is it just me, or others also cannot see debug messages in the gtm proxy
log?

That's very annoying and does not help to sort out any issues at all :-|

I suspect the file descriptors must be getting messed up. Maybe that also
explains why it does not start from inside a script?

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

[Postgres-xc-developers] [JDBC Regression] Fix wrongly written boolean tests

[Abbas B. <abb...@en...>]

Hi,
PFA patch to fix wrongly written boolean tests, patch comments explain the
errors and the fix.

-- 
*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>

[Postgres-xc-developers] [JDBC Regression] Fix for XC does not support serializable transactions

[Abbas B. <abb...@en...>]

Hi,
PFA patch to make sure that JDBC regression skips tests for serializable
transactions.

-- 
*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>

[Postgres-xc-developers] [JDBC Regression] Fix a spelling mistake

[Abbas B. <abb...@en...>]

Hi
PFA patch to fix a spelling mistake.

-- 
*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>

[Postgres-xc-developers] [JDBC Regression] XC does not support binary transfer of fields

[Abbas B. <abb...@en...>]

Hi,
PFA patch to make sure that JDBC regression does not use binary transfer of
fields since XC does not support it.

-- 
*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>

Re: [Postgres-xc-developers] Save Point

[Tomasz S. <str...@gm...>]

Hi,

I am working with alfresco system and i want postgresxc as database to 
increase performence. Alfresco use funcionality "save point" when is 
working with database and i don't want interfere in source code because 
much modules and core use this funcionality.

Regards

W dniu 2013-08-02 03:36, 鈴木 幸市 pisze:
> Yes.
>
> We had similar ML thread on this.   Implementation will not be too 
> tough so I'm curious about the use case and how serious it is.
>
> Regards;
> ---
> Koichi Suzuki
>
> On 2013/08/02, at 9:23, Michael Paquier <mic...@gm... 
> <mailto:mic...@gm...>> wrote:
>
>>
>>
>>
>> On Thu, Aug 1, 2013 at 6:45 PM, Tomasz Straszewski 
>> <str...@gm... <mailto:str...@gm...>> 
>> wrote:
>>
>>     Is there chance to create "save point" functionality?. Now this
>>     is very
>>     important for me, because i can't use postgres xc without this
>>     functionality.
>>
>> It shouldn't be that hard to implement, just that this projects lacks 
>> active developers (who perhaps themselves lack time...) that could 
>> spend time on it. I recall that the priority for this feature very 
>> not that high, but this can evolve based on demand.
>>
>> Regards,
>> -- 
>> Michael
>> ------------------------------------------------------------------------------
>> Get your SQL database under version control now!
>> Version control is standard for application code, but databases havent
>> caught up. So what steps can you take to put your SQL databases under
>> version control? Why should you start doing it? Read more to find out.
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>

Re: [Postgres-xc-developers] About the log output of the BARRIER

[Nikhil S. <ni...@st...>]

+1 for DEBUG1

Regards,
Nikhils

On Fri, Aug 2, 2013 at 8:11 AM, Michael Paquier
<mic...@gm...>wrote:

>
>
>
> On Fri, Aug 2, 2013 at 10:35 AM, 鈴木 幸市 <ko...@in...> wrote:
>
>> Thank you Michael for the input.
>>
>> DEBUG2 message level will get some more information on execution of
>> barrier.   You may have enormous amount of other messages in the log too
>> though.
>>
> DEBUG2 is perhaps too verbose. Why not DEBUG? I don't expect production
> systems to set log level to a value that high.
> --
> Michael
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&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

Re: [Postgres-xc-developers] About the log output of the BARRIER

[Michael P. <mic...@gm...>]

On Fri, Aug 2, 2013 at 10:35 AM, 鈴木 幸市 <ko...@in...> wrote:

> Thank you Michael for the input.
>
> DEBUG2 message level will get some more information on execution of
> barrier.   You may have enormous amount of other messages in the log too
> though.
>
DEBUG2 is perhaps too verbose. Why not DEBUG? I don't expect production
systems to set log level to a value that high.
-- 
Michael

Re: [Postgres-xc-developers] Save Point

[鈴木 幸市 <ko...@in...>]

Yes.

We had similar ML thread on this.   Implementation will not be too tough so I'm curious about the use case and how serious it is.

Regards;
---
Koichi Suzuki

On 2013/08/02, at 9:23, Michael Paquier <mic...@gm...> wrote:

> 
> 
> 
> On Thu, Aug 1, 2013 at 6:45 PM, Tomasz Straszewski <str...@gm...> wrote:
> Is there chance to create "save point" functionality?. Now this is very
> important for me, because i can't use postgres xc without this
> functionality.
> It shouldn't be that hard to implement, just that this projects lacks active developers (who perhaps themselves lack time...) that could spend time on it. I recall that the priority for this feature very not that high, but this can evolve based on demand.
> 
> Regards,
> -- 
> Michael
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent 
> caught up. So what steps can you take to put your SQL databases under 
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

Re: [Postgres-xc-developers] About the log output of the BARRIER

[鈴木 幸市 <ko...@in...>]

Thank you Michael for the input.

DEBUG2 message level will get some more information on execution of barrier.   You may have enormous amount of other messages in the log too though.

Regards;
---
Koichi Suzuki

On 2013/08/02, at 9:02, Michael Paquier <mic...@gm...> wrote:

> 
> 
> 
> On Thu, Aug 1, 2013 at 5:20 PM, 上泉 英二 <uwa...@as...> wrote:
> Coordinator1 outputs a log of BARRIER.
> ------------------------------------------
> 2013-08-01 14:31:58 JST [local] postgres postgres 100116 41DEBUG:  00000: CREATE BARRIER request received
> ...
> omission
> ...
> 2013-08-01 14:31:58 JST [local] postgres postgres 100116 63DEBUG:  00000: Successfully completed CREATE BARRIER <barrier01> END command on all nodes
> ------------------------------------------
> 
> Coordinator2 and Datanode1,2 doesn't outputs a log of BARRIER.
> Those messages inform you that the BARRIER has been correctly created on *all* the nodes, and not on each node individually. So having this message only on the Coordinator from which the sql has been launched is perfectly fine. CREATE BARRIER just adds an xlog record to mark the barrier consistently on the remote nodes, and Postgres does not log any messages when adding an XLOG record each time even for other things like checkpoints. IMO, in this feature it would not make much sense to add a log message that a local barrier has been created on remote nodes except for debugging, the essential point being that you are sure that barrier has been created on *all* the nodes. Even if the coordinator you used for hte barrier creation goes down, I highly doubt that a user would be crazy enough to take the time to look at the logs of all the Datanodes to see if a given barrier record has been created correctly everywhere. You would simply re-run the command until it succeeds.
> 
> Thoughts about the addition of a debug message?
> -- 
> Michael
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent 
> caught up. So what steps can you take to put your SQL databases under 
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

Re: [Postgres-xc-developers] Save Point

[Michael P. <mic...@gm...>]

On Thu, Aug 1, 2013 at 6:45 PM, Tomasz Straszewski <
str...@gm...> wrote:

> Is there chance to create "save point" functionality?. Now this is very
> important for me, because i can't use postgres xc without this
> functionality.
>
It shouldn't be that hard to implement, just that this projects lacks
active developers (who perhaps themselves lack time...) that could spend
time on it. I recall that the priority for this feature very not that high,
but this can evolve based on demand.

Regards,
-- 
Michael

Re: [Postgres-xc-developers] About the log output of the BARRIER

[Michael P. <mic...@gm...>]

On Thu, Aug 1, 2013 at 5:20 PM, 上泉 英二 <uwa...@as...>wrote:

> Coordinator1 outputs a log of BARRIER.
> ------------------------------------------
> 2013-08-01 14:31:58 JST [local] postgres postgres 100116 41DEBUG:  00000:
> CREATE BARRIER request received
> ...
> omission
> ...
> 2013-08-01 14:31:58 JST [local] postgres postgres 100116 63DEBUG:  00000:
> Successfully completed CREATE BARRIER <barrier01> END command on all nodes
> ------------------------------------------
>
> Coordinator2 and Datanode1,2 doesn't outputs a log of BARRIER.
>
Those messages inform you that the BARRIER has been correctly created on
*all* the nodes, and not on each node individually. So having this message
only on the Coordinator from which the sql has been launched is perfectly
fine. CREATE BARRIER just adds an xlog record to mark the barrier
consistently on the remote nodes, and Postgres does not log any messages
when adding an XLOG record each time even for other things like
checkpoints. IMO, in this feature it would not make much sense to add a log
message that a local barrier has been created on remote nodes except for
debugging, the essential point being that you are sure that barrier has
been created on *all* the nodes. Even if the coordinator you used for hte
barrier creation goes down, I highly doubt that a user would be crazy
enough to take the time to look at the logs of all the Datanodes to see if
a given barrier record has been created correctly everywhere. You would
simply re-run the command until it succeeds.

Thoughts about the addition of a debug message?
-- 
Michael

Re: [Postgres-xc-developers] try install MOODLE using postgresxc

[Michael P. <mic...@gm...>]

On Thu, Aug 1, 2013 at 6:14 PM, Afonso Bione <aag...@gm...> wrote:

> Dear friends,
>
> I´d like to ask your help once again to continue the installation of
> Moodle,
> I just created the database in all nodes successfully. But In moodle
> installation got this error message:
>
> *Debug info:* ERROR: Cannot create index whose evaluation cannot be
> enforced to remote nodes
> CREATE UNIQUE INDEX mdl_conf_nam_uix ON mdl_config (name)
>
Change the distribution of your table. In XC, a unique index evaluation
needs to be done at the Datanode level and cannot be done on Coordinators.
So in this case, you need either to change mdl_conf_nam_uix to a replicated
table (in this case you impact performance, but create all kinds of
indexes), or have its distribution key set up as "name" to be sure that the
uniqueness of a given column value is evaluated on a single remote Datanode.
-- 
Michael

[Postgres-xc-developers] Save Point

[Tomasz S. <str...@gm...>]

Hi,

Is there chance to create "save point" functionality?. Now this is very 
important for me, because i can't use postgres xc without this 
functionality.

Regards

[Postgres-xc-developers] try install MOODLE using postgresxc

[Afonso B. <aag...@gm...>]

Dear friends,

I´d like to ask your help once again to continue the installation of
Moodle,
I just created the database in all nodes successfully. But In moodle
installation got this error message:

*Debug info:* ERROR: Cannot create index whose evaluation cannot be
enforced to remote nodes
CREATE UNIQUE INDEX mdl_conf_nam_uix ON mdl_config (name)
Error code: ddlexecuteerror
*Stack trace:*

   - line 432 of /lib/dml/moodle_database.php:
   ddl_change_structure_exception thrown
   - line 248 of /lib/dml/pgsql_native_moodle_database.php: call to
   moodle_database->query_end()
   - line 646 of /lib/dml/pgsql_native_moodle_database.php: call to
   pgsql_native_moodle_database->query_end()
   - line 88 of /lib/ddl/database_manager.php: call to
   pgsql_native_moodle_database->change_database_structure()
   - line 77 of /lib/ddl/database_manager.php: call to
   database_manager->execute_sql()
   - line 415 of /lib/ddl/database_manager.php: call to
   database_manager->execute_sql_arr()
   - line 367 of /lib/ddl/database_manager.php: call to
   database_manager->install_from_xmldb_structure()
   - line 1428 of /lib/upgradelib.php: call to
   database_manager->install_from_xmldb_file()
   - line 180 of /admin/index.php: call to install_core()


Can you help me?

Best Regards