Menu
▾
▴
postgres-xc-developers — Postgres-XC hackers and developers
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(10) |
May
(17) |
Jun
(3) |
Jul
|
Aug
|
Sep
(8) |
Oct
(18) |
Nov
(51) |
Dec
(74) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(47) |
Feb
(44) |
Mar
(44) |
Apr
(102) |
May
(35) |
Jun
(25) |
Jul
(56) |
Aug
(69) |
Sep
(32) |
Oct
(37) |
Nov
(31) |
Dec
(16) |
| 2012 |
Jan
(34) |
Feb
(127) |
Mar
(218) |
Apr
(252) |
May
(80) |
Jun
(137) |
Jul
(205) |
Aug
(159) |
Sep
(35) |
Oct
(50) |
Nov
(82) |
Dec
(52) |
| 2013 |
Jan
(107) |
Feb
(159) |
Mar
(118) |
Apr
(163) |
May
(151) |
Jun
(89) |
Jul
(106) |
Aug
(177) |
Sep
(49) |
Oct
(63) |
Nov
(46) |
Dec
(7) |
| 2014 |
Jan
(65) |
Feb
(128) |
Mar
(40) |
Apr
(11) |
May
(4) |
Jun
(8) |
Jul
(16) |
Aug
(11) |
Sep
(4) |
Oct
(1) |
Nov
(5) |
Dec
(16) |
| 2015 |
Jan
(5) |
Feb
|
Mar
(2) |
Apr
(5) |
May
(4) |
Jun
(12) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Ashutosh B. <ash...@en...> - 2013-09-10 08:20:32
|
Unrelated to your patch, I think, we should now change the way we are handling hash distribution. Instead of having switch cases to get the hash functions, to decide whether a certain column is distributable, we should really be looking up the pg_type catalogs. This has following advantages 1. hashing for distribution would be inline with rest of the hashing (hash joins for example), in the server 2. We don't need to keep adding datatypes to switch cases. Any data type with a hash function would be hash-distributable. Only thing is we shouldn't allow the hash function of a data type to be changed if there is a distributed table based on this hash function. 3. Tables can be distributed by user defined types which have hash functions. This was serious flaw in the previous design, which needs to be corrected before we can add new types to distribution. Same would, then be applicable for modulo distribution where existence of % operator with integer input and integer output can be used. On Tue, Sep 10, 2013 at 1:00 PM, Andrei Martsinchyk < and...@gm...> wrote: > Hello, > > PostgresXC does not support hash distribution by UUID data type. > Attached a small patch that enables the feature. > > -- > Andrei Martsinchyk > > StormDB - http://www.stormdb.com > The Database Cloud > > > > ------------------------------------------------------------------------------ > How ServiceNow helps IT people transform IT departments: > 1. Consolidate legacy IT systems to a single system of record for IT > 2. Standardize and globalize service processes across IT > 3. Implement zero-touch automation to replace manual, redundant tasks > http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company |
|
From: Koichi S. <koi...@gm...> - 2013-09-09 01:04:51
|
Thanks Michael for the work. --- Koichi Suzuki 2013/9/7 Andrei Martsinchyk <and...@gm...> > Hi, > > A segmentation fault happens in the XC if a not empty schema is renamed. > That happens because performRename function is passing parameter of > Relation data type instead of expected Relation * > Please find fix attached. > > -- > Andrei Martsinchyk > > StormDB - http://www.stormdb.com > The Database Cloud > > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > |
|
From: Michael P. <mic...@gm...> - 2013-09-07 09:26:55
|
On Sat, Sep 7, 2013 at 1:13 AM, Andrei Martsinchyk <and...@gm...> wrote: > A segmentation fault happens in the XC if a not empty schema is renamed. > That happens because performRename function is passing parameter of Relation > data type instead of expected Relation * > Please find fix attached. Committed. This big was only present on REL1_0_STABLE. -- Michael |
|
From: Koichi S. <koi...@gm...> - 2013-09-05 08:57:15
|
Year, I applied this to all the stable branches, which will be out at the next chance of the minor release. Regards; --- Koichi Suzuki 2013/9/5 Ashutosh Bapat <ash...@en...> > The commit 9b1cd1ef2e746b9d68085ecd37eabaa38e2a82f1 > > > On Thu, Sep 5, 2013 at 1:50 PM, Michael Paquier <mic...@gm... > > wrote: > >> On Thu, Sep 5, 2013 at 4:44 PM, Koichi Suzuki <koi...@gm...> >> wrote: >> > Thank you Pavan. I've found some more inaccurate headers. I'd like >> to >> > correct them for all the releases. Because this one needs urgent >> > correction, I will commit it promptly. >> This might have been here for ages, perhaps even the beginning of the >> project. >> -- >> Michael >> >> >> ------------------------------------------------------------------------------ >> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! >> Discover the easy way to master current and previous Microsoft >> technologies >> and advance your career. Get an incredible 1,500+ hours of step-by-step >> tutorial videos with LearnDevNow. Subscribe today and save! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> > > > > -- > Best Wishes, > Ashutosh Bapat > EnterpriseDB Corporation > The Postgres Database Company > |
|
From: Pavan D. <pav...@gm...> - 2013-09-05 08:56:08
|
On Thu, Sep 5, 2013 at 1:14 PM, Koichi Suzuki <koi...@gm...> wrote: > Thank you Pavan. I've found some more inaccurate headers. I'd like to > correct them for all the releases. Because this one needs urgent > correction, I will commit it promptly. > Thanks a lot. Thanks, Pavan -- Pavan Deolasee http://www.linkedin.com/in/pavandeolasee |
|
From: Ashutosh B. <ash...@en...> - 2013-09-05 08:27:59
|
The commit 9b1cd1ef2e746b9d68085ecd37eabaa38e2a82f1 On Thu, Sep 5, 2013 at 1:50 PM, Michael Paquier <mic...@gm...>wrote: > On Thu, Sep 5, 2013 at 4:44 PM, Koichi Suzuki <koi...@gm...> > wrote: > > Thank you Pavan. I've found some more inaccurate headers. I'd like to > > correct them for all the releases. Because this one needs urgent > > correction, I will commit it promptly. > This might have been here for ages, perhaps even the beginning of the > project. > -- > Michael > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company |
|
From: Michael P. <mic...@gm...> - 2013-09-05 08:20:36
|
On Thu, Sep 5, 2013 at 4:44 PM, Koichi Suzuki <koi...@gm...> wrote: > Thank you Pavan. I've found some more inaccurate headers. I'd like to > correct them for all the releases. Because this one needs urgent > correction, I will commit it promptly. This might have been here for ages, perhaps even the beginning of the project. -- Michael |
|
From: Koichi S. <koi...@gm...> - 2013-09-05 07:44:52
|
Thank you Pavan. I've found some more inaccurate headers. I'd like to correct them for all the releases. Because this one needs urgent correction, I will commit it promptly. Regards; --- Koichi Suzuki 2013/9/5 Pavan Deolasee <pav...@gm...> > Hello All, > > I see that the pgxc_class.h file in the repository has EnterpriseDB > license header. I am very sure this is just an oversight since the entire > project is under PostgreSQL license. Nevertheless it will be a good idea to > correct the same with EDB's consent: > > > https://github.com/postgres-xc/postgres-xc/blob/master/src/include/catalog/pgxc_class.h > > Thanks, > Pavan > > -- > Pavan Deolasee > http://www.linkedin.com/in/pavandeolasee > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > |
|
From: Pavan D. <pav...@gm...> - 2013-09-05 06:01:01
|
Hello All, I see that the pgxc_class.h file in the repository has EnterpriseDB license header. I am very sure this is just an oversight since the entire project is under PostgreSQL license. Nevertheless it will be a good idea to correct the same with EDB's consent: https://github.com/postgres-xc/postgres-xc/blob/master/src/include/catalog/pgxc_class.h Thanks, Pavan -- Pavan Deolasee http://www.linkedin.com/in/pavandeolasee |
|
From: 鈴木 幸市 <ko...@in...> - 2013-09-05 01:30:08
|
Good news from Mason! --- Koichi Suzuki Begin forwarded message: 差出人: Mason Sharp <ma...@st...<mailto:ma...@st...>> 件名: [Postgres-xc-general] Postgres-XC 1.1 RPMs 日時: 2013年9月5日 10:16:29 JST 宛先: postgres-xc-general <pos...@li...<mailto:pos...@li...>> StormDB has released RPMs for Postgres-XC version 1.1 here: http://yum.stormdb.com/repos/Postgres-XC/1.1.0/ Enjoy! -- Mason Sharp StormDB - http://www.stormdb.com<http://www.stormdb.com/> The Database Cloud Postgres-XC Support and Services ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk_______________________________________________ Postgres-xc-general mailing list Pos...@li... https://lists.sourceforge.net/lists/listinfo/postgres-xc-general |
|
From: Pavan D. <pav...@gm...> - 2013-09-04 11:14:17
|
On Wed, Sep 4, 2013 at 11:08 AM, Amit Khandekar < ami...@en...> wrote: > Just to keep everyone aware... to support savepoints, it is required to > implement the underlying functionality, namely subtransactions. > Subtransactions are used in multiples scenarios. Besides savepoints, the > procedural languages like pl/pgsql and pl/perl also use subtransactions. > Due to the lack of subtransaction support, the exception blocks in pl/pgsql > do not work currently. > Right. One reason why I delayed implementing SAVEPOINT and subtraction support when I initially wrote transaction management is because first we did not have a way for datanodes to talk to GTM directly. Subsequently we added that for auto vacuum etc. Apart from that, especially for internal subtransaction, we will need careful deliberation since such transactions will not be visible on the coordinators. > So rather than propagating SAVEPOINT command to the cluster nodes, we need > to propagate some commands at some point when CommitSubTransaction() and > BeginInternalSubTransaction() are called. There is currently no explicit > SQL command to commit a subtransaction, or start a subtransaction. > SAVEPOINT command can be used to begin a remote subtransaction block. > Right. That's what we would need. > But there does not seem to be a way to commit that sub-transaction block > remotely. > > Well, you can use RELEASE SAVEPOINT to commit a subtransaction and ROLLBACK TO SAVEPOINT to abort it. BTW, named and unnamed savepoints will also need special handling. My 2 cents. Thanks, Pavan -- Pavan Deolasee http://www.linkedin.com/in/pavandeolasee |
|
From: Amit K. <ami...@en...> - 2013-09-04 06:04:41
|
Just to keep everyone aware... to support savepoints, it is required to implement the underlying functionality, namely subtransactions. Subtransactions are used in multiples scenarios. Besides savepoints, the procedural languages like pl/pgsql and pl/perl also use subtransactions. Due to the lack of subtransaction support, the exception blocks in pl/pgsql do not work currently. So rather than propagating SAVEPOINT command to the cluster nodes, we need to propagate some commands at some point when CommitSubTransaction() and BeginInternalSubTransaction() are called. There is currently no explicit SQL command to commit a subtransaction, or start a subtransaction. SAVEPOINT command can be used to begin a remote subtransaction block. But there does not seem to be a way to commit that sub-transaction block remotely. This is just some food for thought in case somebody is thinking of implementing the functionality. There might be many more issues, but not sure right now. There is nothing to handle 2PC for subtransactions because there does not seem to be a corresponding PREPARE TRANSACTION for subtransactions. But possibly there could be some way out. On 3 September 2013 23:12, Leonard Boyce <le...@si...> wrote: > Hi Pavan, > > Unfortunately we do not have the expertise to tackle this in-house. A > "bounty" on the feature may make sense, but without understanding the scale > or complexity of the feature itself it is extremely difficult to even > propose such to my higher ups. > With other projects it would be easier to gauge the 'value' as there is > (in may cases) a history of previous bounties. > > Any help or direction here would be appreciated. > Thanks, > Leonard > > > On Sun, Sep 1, 2013 at 11:32 PM, Pavan Deolasee <pav...@gm...>wrote: > >> On Sat, Aug 31, 2013 at 1:33 AM, Leonard Boyce <le...@si...>wrote: >> >>> Hi all, >>> >>> We've been eagerly following XC since it's first announcement and are >>> eager to start testing XC. We had to wait for trigger support, but it >>> seems our only remaining barrier is no support for savepoints. >>> >>> >> Apart from waiting on the team to implement the missing feature, do you >> think you or someone else in your organisation has skills/time to give it a >> shot ? IMHO the core team will have limited time and resources to keep >> adding new features. Another possibility is to fund the development so that >> someone who has time and skills can speedtrack the development. That's a >> model often used by other open source projects including PostgreSQL. >> >> Thanks, >> Pavan >> -- >> Pavan Deolasee >> http://www.linkedin.com/in/pavandeolasee >> > > > > -- > Kind regards, > Leonard Boyce > http://www.siftlogic.com > (m) 305-3351268 > (s) leonard.boyce > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > |
|
From: Leonard B. <le...@si...> - 2013-09-03 17:42:47
|
Hi Pavan, Unfortunately we do not have the expertise to tackle this in-house. A "bounty" on the feature may make sense, but without understanding the scale or complexity of the feature itself it is extremely difficult to even propose such to my higher ups. With other projects it would be easier to gauge the 'value' as there is (in may cases) a history of previous bounties. Any help or direction here would be appreciated. Thanks, Leonard On Sun, Sep 1, 2013 at 11:32 PM, Pavan Deolasee <pav...@gm...>wrote: > On Sat, Aug 31, 2013 at 1:33 AM, Leonard Boyce <le...@si...>wrote: > >> Hi all, >> >> We've been eagerly following XC since it's first announcement and are >> eager to start testing XC. We had to wait for trigger support, but it >> seems our only remaining barrier is no support for savepoints. >> >> > Apart from waiting on the team to implement the missing feature, do you > think you or someone else in your organisation has skills/time to give it a > shot ? IMHO the core team will have limited time and resources to keep > adding new features. Another possibility is to fund the development so that > someone who has time and skills can speedtrack the development. That's a > model often used by other open source projects including PostgreSQL. > > Thanks, > Pavan > -- > Pavan Deolasee > http://www.linkedin.com/in/pavandeolasee > -- Kind regards, Leonard Boyce http://www.siftlogic.com (m) 305-3351268 (s) leonard.boyce |
|
From: Masataka S. <pg...@gm...> - 2013-09-02 06:58:25
|
I meant that your patch is needless to fix. I'm sorry to confuse you. But your build.local.properties is also fine. Regards. On Wed, Aug 21, 2013 at 12:46 PM, Abbas Butt <abb...@en...> wrote: > A sample build.local.properties file is attached for reference. > > > On Mon, Aug 5, 2013 at 12:55 PM, Masataka Saito <pg...@gm...> wrote: >> >> 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 > > > > > -- > -- > 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 |
|
From: Michael P. <mic...@gm...> - 2013-09-02 04:58:57
|
On Mon, Sep 2, 2013 at 1:20 PM, Ashutosh Bapat <ash...@en...> wrote: > +1. There's limit on what a handful of core members can do. Definitely. >> Another possibility is to fund the development so that someone who >> has time and skills can speedtrack the development. That's a >> model often used by other open source projects including PostgreSQL. And this would make as well make new people getting more accustomed to XC. -- Michael |
|
From: Nikhil S. <ni...@st...> - 2013-09-02 04:36:09
|
> Apart from waiting on the team to implement the missing feature, do you > think you or someone else in your organisation has skills/time to give it a > shot ? IMHO the core team will have limited time and resources to keep > adding new features. Another possibility is to fund the development so that > someone who has time and skills can speedtrack the development. That's a > model often used by other open source projects including PostgreSQL. > > +1 Regards, Nikhils -- StormDB - http://www.stormdb.com The Database Cloud |
|
From: 鈴木 幸市 <ko...@in...> - 2013-09-02 04:26:29
|
+1 too. Core members will be more than happy to review and include submitted patch. --- Koichi Suzuki On 2013/09/02, at 13:20, Ashutosh Bapat <ash...@en...<mailto:ash...@en...>> wrote: +1. There's limit on what a handful of core members can do. On Mon, Sep 2, 2013 at 9:02 AM, Pavan Deolasee <pav...@gm...<mailto:pav...@gm...>> wrote: On Sat, Aug 31, 2013 at 1:33 AM, Leonard Boyce <le...@si...<mailto:le...@si...>> wrote: Hi all, We've been eagerly following XC since it's first announcement and are eager to start testing XC. We had to wait for trigger support, but it seems our only remaining barrier is no support for savepoints. Apart from waiting on the team to implement the missing feature, do you think you or someone else in your organisation has skills/time to give it a shot ? IMHO the core team will have limited time and resources to keep adding new features. Another possibility is to fund the development so that someone who has time and skills can speedtrack the development. That's a model often used by other open source projects including PostgreSQL. Thanks, Pavan -- Pavan Deolasee http://www.linkedin.com/in/pavandeolasee ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ Postgres-xc-developers mailing list Pos...@li...<mailto:Pos...@li...> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk_______________________________________________ Postgres-xc-developers mailing list Pos...@li... https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: Ashutosh B. <ash...@en...> - 2013-09-02 04:20:31
|
+1. There's limit on what a handful of core members can do. On Mon, Sep 2, 2013 at 9:02 AM, Pavan Deolasee <pav...@gm...>wrote: > On Sat, Aug 31, 2013 at 1:33 AM, Leonard Boyce <le...@si...>wrote: > >> Hi all, >> >> We've been eagerly following XC since it's first announcement and are >> eager to start testing XC. We had to wait for trigger support, but it >> seems our only remaining barrier is no support for savepoints. >> >> > Apart from waiting on the team to implement the missing feature, do you > think you or someone else in your organisation has skills/time to give it a > shot ? IMHO the core team will have limited time and resources to keep > adding new features. Another possibility is to fund the development so that > someone who has time and skills can speedtrack the development. That's a > model often used by other open source projects including PostgreSQL. > > Thanks, > Pavan > -- > Pavan Deolasee > http://www.linkedin.com/in/pavandeolasee > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company |
|
From: Pavan D. <pav...@gm...> - 2013-09-02 03:32:30
|
On Sat, Aug 31, 2013 at 1:33 AM, Leonard Boyce <le...@si...>wrote: > Hi all, > > We've been eagerly following XC since it's first announcement and are > eager to start testing XC. We had to wait for trigger support, but it > seems our only remaining barrier is no support for savepoints. > > Apart from waiting on the team to implement the missing feature, do you think you or someone else in your organisation has skills/time to give it a shot ? IMHO the core team will have limited time and resources to keep adding new features. Another possibility is to fund the development so that someone who has time and skills can speedtrack the development. That's a model often used by other open source projects including PostgreSQL. Thanks, Pavan -- Pavan Deolasee http://www.linkedin.com/in/pavandeolasee |
|
From: Koichi S. <koi...@gm...> - 2013-09-02 01:07:29
|
Thanks a lot for the patch. The code looks okay. I will commit it after the test. Regards; --- Koichi Suzuki 2013/8/30 Michael Paquier <mic...@gm...> > On Fri, Aug 30, 2013 at 6:06 PM, Nikhil Sontakke <ni...@st...> > wrote: > > A small patch to change the log level of one particular message from LOG > to > > DEBUG1. In case a standby is configured, for each connection done to the > > GTM, a corresponding call log gets added in the log file. > > > > "Connection established with standby. - 0x2a1dd60" > > > > The log file can grow up in size unnecessarily (we have seen 5GB+ sized > log > > files!) with these not so useful messages given that we already log if > the > > connection to the Standby fails. > > > > This patch applies on both head and REL1.1 > +1 for applying that to 1.1 as well. This is not really a bug fix, but > it has been an annoyance for ages, and parsing log files of many GBs > is always a problem. > -- > Michael > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > |
|
From: 鈴木 幸市 <ko...@in...> - 2013-09-02 00:59:43
|
Right. Now we should begin discussing what would be the priority for the development beyond 1.2. In 1.2, we're concentrating on the following: 1. More test for jdbc, through jdbc regression and additional test (mostly subquery and aggregate), 2. Planner improvement for subquery and aggregate in the standard planner (first round, we need a couple of additional rounds for this), 3. Quicker merge with PG9.3. Unfortunately, savepoint is not in the highest priority. To me, general support of constraint has higher priority. This couple of months, we're having many mailing list thread related to this. I'd like to begin the discussion of our practical roadmap beyond 1.2 soon. Regards; --- Koichi Suzuki On 2013/08/31, at 17:43, Michael Paquier <mic...@gm...> wrote: > On Sat, Aug 31, 2013 at 5:03 AM, Leonard Boyce <le...@si...> wrote: >> Maybe this use-case will bump the feature priority a touch. > The more the demand, the more it would get on the priority list of > developers. This is not the first demand for savepoints I am seeing > since 1.1beta has been released. Suzuki-san? > -- > Michael > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > |
|
From: Michael P. <mic...@gm...> - 2013-08-31 08:43:38
|
On Sat, Aug 31, 2013 at 5:03 AM, Leonard Boyce <le...@si...> wrote: > Maybe this use-case will bump the feature priority a touch. The more the demand, the more it would get on the priority list of developers. This is not the first demand for savepoints I am seeing since 1.1beta has been released. Suzuki-san? -- Michael |
|
From: Leonard B. <le...@si...> - 2013-08-30 20:32:35
|
Hi all, We've been eagerly following XC since it's first announcement and are eager to start testing XC. We had to wait for trigger support, but it seems our only remaining barrier is no support for savepoints. I've seen some recent activity on this question and wanted to chime in with our use-case. We access Pg from Erlang and use savepoints extensively to implement update-insert / insert-update (with loop limits) logic within transactions which require safe modification of other data *prior* to the insert-update / update-insert. Yes, we could move all this into db functions, but that would take a fairly large effort on our part and it makes code management more complex for us. Maybe this use-case will bump the feature priority a touch. Kind regards, Leonard |
|
From: Michael P. <mic...@gm...> - 2013-08-30 12:19:39
|
On Fri, Aug 30, 2013 at 6:06 PM, Nikhil Sontakke <ni...@st...> wrote: > A small patch to change the log level of one particular message from LOG to > DEBUG1. In case a standby is configured, for each connection done to the > GTM, a corresponding call log gets added in the log file. > > "Connection established with standby. - 0x2a1dd60" > > The log file can grow up in size unnecessarily (we have seen 5GB+ sized log > files!) with these not so useful messages given that we already log if the > connection to the Standby fails. > > This patch applies on both head and REL1.1 +1 for applying that to 1.1 as well. This is not really a bug fix, but it has been an annoyance for ages, and parsing log files of many GBs is always a problem. -- Michael |
|
From: Michael P. <mic...@gm...> - 2013-08-30 12:17:57
|
On Fri, Aug 30, 2013 at 4:36 PM, Abbas Butt <abb...@en...> wrote: > Can you share the query and table structure that you are using to perform > the test? You can obscure the column/table names if they are part of some > proprietary application. > The comment you mentioned in execRemote.c is relevant for DMLs only but you > said that your's is a SELECT, isn't it? Adding the output of EXPLAIN VERBOSE could also help to understand the plan your query is using. -- Michael |
261 messages has been excluded from this view by a project administrator.
