Menu
▾
▴
postgres-xc-developers
|
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-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: 鈴木 幸市 <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: 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: 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: 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: 鈴木 幸市 <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: 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: 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: 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: 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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X