Menu
▾
▴
postgres-xc-developers
|
From: David E. W. <da...@ju...> - 2014-01-31 00:27:28
|
XCers,
Sqitch has a query that looks like this:
INSERT INTO tags (
tag_id
, tag
, project
, change_id
, note
, committer_name
, committer_email
, planned_at
, planner_name
, planner_email
)
SELECT tid, tg, proj, chid, n, name, email, at, pname, pemail FROM ( VALUES
(?, ?, ?, ?, ?, ?, ?, ?::timestamptz, ?, ?)
) i(tid, tg, proj, chid, n, name, email, at, pname, pemail)
LEFT JOIN tags ON i.tid = tags.tag_id
WHERE tags.tag_id IS NULL
Works fine on 8.4-9.3, but XC does not like it:
ERROR: unexpected varno 6 in JOIN RTE 5
I have no idea what that means. I tried renaming some of the column aliases in the VALUES subselect, but it made not difference. Any ideas?
Thanks,
David
|
|
From: Koichi S. <koi...@gm...> - 2014-01-31 01:35:48
|
Ashutosh, do you have a time to look into it? --- Koichi Suzuki 2014-01-31 David E. Wheeler <da...@ju...>: > XCers, > > Sqitch has a query that looks like this: > > INSERT INTO tags ( > tag_id > , tag > , project > , change_id > , note > , committer_name > , committer_email > , planned_at > , planner_name > , planner_email > ) > SELECT tid, tg, proj, chid, n, name, email, at, pname, pemail FROM ( VALUES > (?, ?, ?, ?, ?, ?, ?, ?::timestamptz, ?, ?) > ) i(tid, tg, proj, chid, n, name, email, at, pname, pemail) > LEFT JOIN tags ON i.tid = tags.tag_id > WHERE tags.tag_id IS NULL > > Works fine on 8.4-9.3, but XC does not like it: > > ERROR: unexpected varno 6 in JOIN RTE 5 > > I have no idea what that means. I tried renaming some of the column aliases in the VALUES subselect, but it made not difference. Any ideas? > > Thanks, > > David > > > > ------------------------------------------------------------------------------ > WatchGuard Dimension instantly turns raw network data into actionable > security intelligence. It gives you real-time visual feedback on key > security issues and trends. Skip the complicated setup - simply import > a virtual appliance and go from zero to informed in seconds. > http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: David E. W. <da...@ju...> - 2014-02-05 01:06:38
|
Hi there, I’d like to release an updated version of Sqitch, but would like to resolve this issue, first. Anyone had a chance to look into it? Thanks, David On Jan 30, 2014, at 5:35 PM, Koichi Suzuki <koi...@gm...> wrote: > Ashutosh, do you have a time to look into it? > > 2014-01-31 David E. Wheeler <da...@ju...>: >> XCers, >> >> Sqitch has a query that looks like this: >> >> INSERT INTO tags ( >> tag_id >> , tag >> , project >> , change_id >> , note >> , committer_name >> , committer_email >> , planned_at >> , planner_name >> , planner_email >> ) >> SELECT tid, tg, proj, chid, n, name, email, at, pname, pemail FROM ( VALUES >> (?, ?, ?, ?, ?, ?, ?, ?::timestamptz, ?, ?) >> ) i(tid, tg, proj, chid, n, name, email, at, pname, pemail) >> LEFT JOIN tags ON i.tid = tags.tag_id >> WHERE tags.tag_id IS NULL >> >> Works fine on 8.4-9.3, but XC does not like it: >> >> ERROR: unexpected varno 6 in JOIN RTE 5 >> >> I have no idea what that means. I tried renaming some of the column aliases in the VALUES subselect, but it made not difference. Any ideas? |
|
From: Abbas B. <abb...@en...> - 2014-02-05 05:24:55
|
Could you please send the table definition of tag? A CREATE TABLE statement would do. On Wed, Feb 5, 2014 at 6:06 AM, David E. Wheeler <da...@ju...>wrote: > Hi there, > > I'd like to release an updated version of Sqitch, but would like to > resolve this issue, first. Anyone had a chance to look into it? > > Thanks, > > David > > On Jan 30, 2014, at 5:35 PM, Koichi Suzuki <koi...@gm...> wrote: > > > Ashutosh, do you have a time to look into it? > > > > 2014-01-31 David E. Wheeler <da...@ju...>: > >> XCers, > >> > >> Sqitch has a query that looks like this: > >> > >> INSERT INTO tags ( > >> tag_id > >> , tag > >> , project > >> , change_id > >> , note > >> , committer_name > >> , committer_email > >> , planned_at > >> , planner_name > >> , planner_email > >> ) > >> SELECT tid, tg, proj, chid, n, name, email, at, pname, > pemail FROM ( VALUES > >> (?, ?, ?, ?, ?, ?, ?, ?::timestamptz, ?, ?) > >> ) i(tid, tg, proj, chid, n, name, email, at, pname, pemail) > >> LEFT JOIN tags ON i.tid = tags.tag_id > >> WHERE tags.tag_id IS NULL > >> > >> Works fine on 8.4-9.3, but XC does not like it: > >> > >> ERROR: unexpected varno 6 in JOIN RTE 5 > >> > >> I have no idea what that means. I tried renaming some of the column > aliases in the VALUES subselect, but it made not difference. Any ideas? > > > > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&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> |
|
From: David E. W. <da...@ju...> - 2014-02-05 05:48:01
|
On Feb 4, 2014, at 9:24 PM, Abbas Butt <abb...@en...> wrote:
> Could you please send the table definition of tag? A CREATE TABLE statement would do.
CREATE TABLE tags (
tag_id TEXT PRIMARY KEY,
tag TEXT NOT NULL,
project TEXT NOT NULL REFERENCES projects(project) ON UPDATE CASCADE,
change_id TEXT NOT NULL REFERENCES changes(change_id) ON UPDATE CASCADE,
note TEXT NOT NULL DEFAULT '',
committed_at TIMESTAMPTZ NOT NULL DEFAULT clock_timestamp(),
committer_name TEXT NOT NULL,
committer_email TEXT NOT NULL,
planned_at TIMESTAMPTZ NOT NULL,
planner_name TEXT NOT NULL,
planner_email TEXT NOT NULL,
UNIQUE(project, tag)
) DISTRIBUTE BY REPLICATION;
Want projects and changes, too?
CREATE TABLE projects (
project TEXT PRIMARY KEY,
uri TEXT NULL UNIQUE,
created_at TIMESTAMPTZ NOT NULL DEFAULT clock_timestamp(),
creator_name TEXT NOT NULL,
creator_email TEXT NOT NULL
) DISTRIBUTE BY REPLICATION;
CREATE TABLE changes (
change_id TEXT PRIMARY KEY,
change TEXT NOT NULL,
project TEXT NOT NULL REFERENCES projects(project) ON UPDATE CASCADE,
note TEXT NOT NULL DEFAULT '',
committed_at TIMESTAMPTZ NOT NULL DEFAULT clock_timestamp(),
committer_name TEXT NOT NULL,
committer_email TEXT NOT NULL,
planned_at TIMESTAMPTZ NOT NULL,
planner_name TEXT NOT NULL,
planner_email TEXT NOT NULL
) DISTRIBUTE BY REPLICATION;
Best,
David
|
|
From: Abbas B. <abb...@en...> - 2014-02-05 06:19:05
|
I had to change the insert query a little bit and had to do some dummy
inserts in projects and changes too, but the query worked fine for me. BTW
I tried on current master, I am not sure which version you are using to
test.
Here are the queries I tried.
After creating the three tables, I did
insert into projects values('?', '?', DEFAULT, '?', '?');
insert into changes values('?', '?', '?', '?', DEFAULT, '?', '?',
clock_timestamp(), '?', '?');
INSERT INTO tags (tag_id, tag, project, change_id, note, committer_name,
committer_email, planned_at, planner_name, planner_email)
SELECT tid, tg, proj, chid, n, name, email, at, pname, pemail FROM ( VALUES
('?', '?', '?', '?', '?', '?', '?', clock_timestamp()::timestamptz, '?',
'?')) i(tid, tg, proj, chid, n, name, email, at, pname, pemail) LEFT JOIN
tags ON i.tid = tags.tag_id WHERE tags.tag_id IS NULL;
Best Regards
On Wed, Feb 5, 2014 at 10:47 AM, David E. Wheeler <da...@ju...>wrote:
> On Feb 4, 2014, at 9:24 PM, Abbas Butt <abb...@en...>
> wrote:
>
> > Could you please send the table definition of tag? A CREATE TABLE
> statement would do.
>
> CREATE TABLE tags (
> tag_id TEXT PRIMARY KEY,
> tag TEXT NOT NULL,
> project TEXT NOT NULL REFERENCES projects(project) ON
> UPDATE CASCADE,
> change_id TEXT NOT NULL REFERENCES changes(change_id) ON
> UPDATE CASCADE,
> note TEXT NOT NULL DEFAULT '',
> committed_at TIMESTAMPTZ NOT NULL DEFAULT clock_timestamp(),
> committer_name TEXT NOT NULL,
> committer_email TEXT NOT NULL,
> planned_at TIMESTAMPTZ NOT NULL,
> planner_name TEXT NOT NULL,
> planner_email TEXT NOT NULL,
> UNIQUE(project, tag)
> ) DISTRIBUTE BY REPLICATION;
>
> Want projects and changes, too?
>
> CREATE TABLE projects (
> project TEXT PRIMARY KEY,
> uri TEXT NULL UNIQUE,
> created_at TIMESTAMPTZ NOT NULL DEFAULT clock_timestamp(),
> creator_name TEXT NOT NULL,
> creator_email TEXT NOT NULL
> ) DISTRIBUTE BY REPLICATION;
>
> CREATE TABLE changes (
> change_id TEXT PRIMARY KEY,
> change TEXT NOT NULL,
> project TEXT NOT NULL REFERENCES projects(project) ON
> UPDATE CASCADE,
> note TEXT NOT NULL DEFAULT '',
> committed_at TIMESTAMPTZ NOT NULL DEFAULT clock_timestamp(),
> committer_name TEXT NOT NULL,
> committer_email TEXT NOT NULL,
> planned_at TIMESTAMPTZ NOT NULL,
> planner_name TEXT NOT NULL,
> planner_email TEXT NOT NULL
> ) DISTRIBUTE BY REPLICATION;
>
> Best,
>
> David
>
>
>
--
--
*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>
|
|
From: David E. W. <da...@ju...> - 2014-02-05 17:04:00
|
On Feb 4, 2014, at 10:18 PM, Abbas Butt <abb...@en...> wrote:
> I had to change the insert query a little bit and had to do some dummy inserts in projects and changes too, but the query worked fine for me. BTW I tried on current master, I am not sure which version you are using to test.
The 1.1 release.
> Here are the queries I tried.
>
> After creating the three tables, I did
>
> insert into projects values('?', '?', DEFAULT, '?', '?');
>
> insert into changes values('?', '?', '?', '?', DEFAULT, '?', '?', clock_timestamp(), '?', '?');
>
> INSERT INTO tags (tag_id, tag, project, change_id, note, committer_name, committer_email, planned_at, planner_name, planner_email)
> SELECT tid, tg, proj, chid, n, name, email, at, pname, pemail FROM ( VALUES ('?', '?', '?', '?', '?', '?', '?', clock_timestamp()::timestamptz, '?', '?')) i(tid, tg, proj, chid, n, name, email, at, pname, pemail) LEFT JOIN tags ON i.tid = tags.tag_id WHERE tags.tag_id IS NULL;
On 1.1:
dwheeler=# insert into sqitch.projects values('?', '?', DEFAULT, '?', '?');
INSERT 0 1
Time: 48.720 ms
dwheeler=# insert into sqitch.changes values('?', '?', '?', '?', DEFAULT, '?', '?', clock_timestamp(), '?', '?');
INSERT 0 1
Time: 43.704 ms
dwheeler=# INSERT INTO sqitch.tags (tag_id, tag, project, change_id, note, committer_name, committer_email, planned_at, planner_name, planner_email)
dwheeler=# INSERT INTO sqitch.tags (tag_id, tag, project, change_id, note, committer_name, committer_email, planned_at, planner_name, planner_email)
dwheeler-# SELECT tid, tg, proj, chid, n, name, email, at, pname, pemail FROM ( VALUES ('?', '?', '?', '?', '?', '?', '?', clock_timestamp()::timestamptz, '?', '?')) i(tid, tg, proj, chid, n, name, email, at, pname, pemail) LEFT JOIN sqitch.tags ON i.tid = tags.tag_id WHERE tags.tag_id IS NULL;
ERROR: unexpected varno 6 in JOIN RTE 5
Time: 4.064 ms
Best,
David
|
|
From: Ahsan H. <ahs...@en...> - 2014-02-06 07:18:00
|
Abbas,
Can you test this with 1.1? Perhaps we fixed this issue in the master which
means that it will be part of 1.2 beta that is planned for this month.
-- Ahsan
On Wed, Feb 5, 2014 at 10:03 PM, David E. Wheeler <da...@ju...>wrote:
> On Feb 4, 2014, at 10:18 PM, Abbas Butt <abb...@en...>
> wrote:
>
> > I had to change the insert query a little bit and had to do some dummy
> inserts in projects and changes too, but the query worked fine for me. BTW
> I tried on current master, I am not sure which version you are using to
> test.
>
> The 1.1 release.
>
> > Here are the queries I tried.
> >
> > After creating the three tables, I did
> >
> > insert into projects values('?', '?', DEFAULT, '?', '?');
> >
> > insert into changes values('?', '?', '?', '?', DEFAULT, '?', '?',
> clock_timestamp(), '?', '?');
> >
> > INSERT INTO tags (tag_id, tag, project, change_id, note, committer_name,
> committer_email, planned_at, planner_name, planner_email)
> > SELECT tid, tg, proj, chid, n, name, email, at, pname, pemail FROM (
> VALUES ('?', '?', '?', '?', '?', '?', '?', clock_timestamp()::timestamptz,
> '?', '?')) i(tid, tg, proj, chid, n, name, email, at, pname, pemail) LEFT
> JOIN tags ON i.tid = tags.tag_id WHERE tags.tag_id IS NULL;
>
> On 1.1:
>
> dwheeler=# insert into sqitch.projects values('?', '?', DEFAULT, '?', '?');
> INSERT 0 1
> Time: 48.720 ms
> dwheeler=# insert into sqitch.changes values('?', '?', '?', '?', DEFAULT,
> '?', '?', clock_timestamp(), '?', '?');
> INSERT 0 1
> Time: 43.704 ms
> dwheeler=# INSERT INTO sqitch.tags (tag_id, tag, project, change_id, note,
> committer_name, committer_email, planned_at, planner_name, planner_email)
> dwheeler=# INSERT INTO sqitch.tags (tag_id, tag, project, change_id, note,
> committer_name, committer_email, planned_at, planner_name, planner_email)
> dwheeler-# SELECT tid, tg, proj, chid, n, name, email, at, pname, pemail
> FROM ( VALUES ('?', '?', '?', '?', '?', '?', '?',
> clock_timestamp()::timestamptz, '?', '?')) i(tid, tg, proj, chid, n, name,
> email, at, pname, pemail) LEFT JOIN sqitch.tags ON i.tid = tags.tag_id
> WHERE tags.tag_id IS NULL;
> ERROR: unexpected varno 6 in JOIN RTE 5
> Time: 4.064 ms
>
> Best,
>
> David
>
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
--
Ahsan Hadi
Snr Director Product Development
EnterpriseDB Corporation
The Enterprise Postgres Company
Phone: +92-51-8358874
Mobile: +92-333-5162114
Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb
This e-mail message (and any attachment) is intended for the use of the
individual or entity to whom it is addressed. This message contains
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.
|
|
From: David E. W. <da...@ju...> - 2014-02-12 17:28:19
|
On Feb 5, 2014, at 11:17 PM, Ahsan Hadi <ahs...@en...> wrote: > Abbas, > > Can you test this with 1.1? Perhaps we fixed this issue in the master which means that it will be part of 1.2 beta that is planned for this month. Hey All, Any word on this? Holding up a release Sqitch till I hear back. Thanks, David |
|
From: Abbas B. <abb...@en...> - 2014-02-14 01:31:02
|
Hi, Would it be possible for you to base the release on 1.2 instead? We have just released 1.2 beta and would soon be going GA. I have tested that the case works fine on 1.2. Regards On Wed, Feb 12, 2014 at 10:28 PM, David E. Wheeler <da...@ju...>wrote: > On Feb 5, 2014, at 11:17 PM, Ahsan Hadi <ahs...@en...> > wrote: > > > Abbas, > > > > Can you test this with 1.1? Perhaps we fixed this issue in the master > which means that it will be part of 1.2 beta that is planned for this month. > > Hey All, > > Any word on this? Holding up a release Sqitch till I hear back. > > Thanks, > > David -- -- *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> |
|
From: David E. W. <da...@ju...> - 2014-02-14 04:12:54
|
On Feb 13, 2014, at 5:30 PM, Abbas Butt <abb...@en...> wrote: > Would it be possible for you to base the release on 1.2 instead? > We have just released 1.2 beta and would soon be going GA. > I have tested that the case works fine on 1.2. I can start working on a 1.2 build soon, yeah. So is 1.1 end-of-lifed? No more work to be done on it? Thanks, David |
|
From: 鈴木 幸市 <ko...@in...> - 2014-02-14 04:20:03
|
Not really although there will be no feature addition in 1.1. I will keep maintaining 1.1 and 1.0 for a while. As I wrote in the note, 1.2 needs at least one improvement of update/delete in replicated tables. It will be good to begin 1.2 work after GA unless you’d like to practice on it. Regards; --- Koichi Suzuki 2014/02/14 13:12、David E. Wheeler <da...@ju...> のメール： > On Feb 13, 2014, at 5:30 PM, Abbas Butt <abb...@en...> wrote: > >> Would it be possible for you to base the release on 1.2 instead? >> We have just released 1.2 beta and would soon be going GA. >> I have tested that the case works fine on 1.2. > > I can start working on a 1.2 build soon, yeah. So is 1.1 end-of-lifed? No more work to be done on it? > > Thanks, > > David > > > ------------------------------------------------------------------------------ > Android apps run on BlackBerry 10 > Introducing the new BlackBerry 10.2.1 Runtime for Android apps. > Now with support for Jelly Bean, Bluetooth, Mapview and more. > Get your Android app in front of a whole new audience. Start now. > http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > |
|
From: David E. W. <da...@ju...> - 2014-02-14 18:54:21
|
On Feb 13, 2014, at 8:19 PM, 鈴木 幸市 <ko...@in...> wrote: > Not really although there will be no feature addition in 1.1. I will keep maintaining 1.1 and 1.0 for a while. As I wrote in the note, 1.2 needs at least one improvement of update/delete in replicated tables. It will be good to begin 1.2 work after GA unless you’d like to practice on it. So, does that mean that there might be a 1.1.1 release with bug fixes? Because this feels like a bug to me. Thanks, David |
|
From: 鈴木 幸市 <ko...@in...> - 2014-02-17 07:13:59
|
1.1 is not suffered by this. The bug was introduced during planner code change to deal with PG planner code change (mainly from automatic updatable views). Regards; --- Koichi Suzuki 2014/02/15 3:54、David E. Wheeler <da...@ju...> のメール： > On Feb 13, 2014, at 8:19 PM, 鈴木 幸市 <ko...@in...> wrote: > >> Not really although there will be no feature addition in 1.1. I will keep maintaining 1.1 and 1.0 for a while. As I wrote in the note, 1.2 needs at least one improvement of update/delete in replicated tables. It will be good to begin 1.2 work after GA unless you’d like to practice on it. > > So, does that mean that there might be a 1.1.1 release with bug fixes? Because this feels like a bug to me. > > Thanks, > > David > > > |
|
From: David E. W. <da...@ju...> - 2014-02-18 19:46:43
|
On Feb 16, 2014, at 11:13 PM, 鈴木 幸市 <ko...@in...> wrote: > 1.1 is not suffered by this. The bug was introduced during planner code change to deal with PG planner code change (mainly from automatic updatable views). I don’t understand. I get this error on 1.1, and Abbas says it is not present in 1.2. That seems like an issue in 1.1 that might be fixable in a 1.1.1 release, should there ever be one. Am I missing something? Best, David |
|
From: Koichi S. <koi...@gm...> - 2014-02-27 02:43:50
|
I may be wrong. The key issue is XC planner may choose CTID as a key to update/delete replicated table rows when whole statement cannot push down to datanodes. I understood this was introduced in 1.2 but this could have been an issue in 1.1 as well. Ashutosh, Abbas, could you clarify this? Regards; --- Koichi Suzuki 2014-02-19 4:46 GMT+09:00 David E. Wheeler <da...@ju...>: > On Feb 16, 2014, at 11:13 PM, 鈴木 幸市 <ko...@in...> wrote: > >> 1.1 is not suffered by this. The bug was introduced during planner code change to deal with PG planner code change (mainly from automatic updatable views). > > I don’t understand. I get this error on 1.1, and Abbas says it is not present in 1.2. That seems like an issue in 1.1 that might be fixable in a 1.1.1 release, should there ever be one. Am I missing something? > > Best, > > David > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: Abbas B. <abb...@en...> - 2014-02-27 16:35:53
|
On Wed, Feb 19, 2014 at 12:46 AM, David E. Wheeler <da...@ju...>wrote: > On Feb 16, 2014, at 11:13 PM, 鈴木 幸市 <ko...@in...> wrote: > > > 1.1 is not suffered by this. The bug was introduced during planner > code change to deal with PG planner code change (mainly from automatic > updatable views). > > I don’t understand. I get this error on 1.1, and Abbas says it is not > present in 1.2. That seems like an issue in 1.1 that might be fixable in a > 1.1.1 release, should there ever be one. Am I missing something? > Sorry for the confusion. We have currently no plans to release 1.1.1. Between 1.1 and 1.2 we have re-factored code in many areas and bug fixes are not easily back portable. > Best, > > David -- -- *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> |
|
From: David E. W. <da...@ju...> - 2014-02-27 17:08:27
|
On Feb 27, 2014, at 8:35 AM, Abbas Butt <abb...@en...> wrote: > Sorry for the confusion. We have currently no plans to release 1.1.1. Between 1.1 and 1.2 we have re-factored code in many areas and bug fixes are not easily back portable. Okay, so 1.0 and 1.1 are no longer maintained or supported. Good to know. Thank you, David |
|
From: Koichi S. <koi...@gm...> - 2014-02-27 23:29:11
|
It is not correct. 1.0 and 1.1 are maintained. Fix of the issue may not be easy though. Regards --- Koichi Suzuki 2014/02/28 2:09 "David E. Wheeler" <da...@ju...>: > On Feb 27, 2014, at 8:35 AM, Abbas Butt <abb...@en...> > wrote: > > > Sorry for the confusion. We have currently no plans to release 1.1.1. > Between 1.1 and 1.2 we have re-factored code in many areas and bug fixes > are not easily back portable. > > Okay, so 1.0 and 1.1 are no longer maintained or supported. Good to know. > > Thank you, > > David > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > |
|
From: David E. W. <da...@ju...> - 2014-02-27 23:33:35
|
On Feb 27, 2014, at 3:29 PM, Koichi Suzuki <koi...@gm...> wrote: > It is not correct. 1.0 and 1.1 are maintained. Fix of the issue may not be easy though. So, maintained, but no plan to release new versions? Sure, some bugs may be too much trouble for a maintained branch, but as Abbas says there are no plans to release new versions, it sounds an awful lot to me like no issues will be fixed, at least not in a release. Best, David |
|
From: 鈴木 幸市 <ko...@in...> - 2014-02-28 06:52:01
|
Sorry, it has not been made open. Similar to PG, I’m planning to release 1.0.3 and 1.1.1 after 1.2GA is out. 1.2GA will be out when replicated table update/delete is fixed. I’m planning to include the following fixes in all the major/minor releases. 1. GTM Proxy fix to handle disconnection from backends: this caused “snapshot not available” error for heavy workloads. 2. Fix restriction to use temporary objects. 3. Fix statement cancellation error to improve random failure in the regression test. Regards; --- Koichi Suzuki 2014/02/28 8:33、David E. Wheeler <da...@ju...> のメール： > On Feb 27, 2014, at 3:29 PM, Koichi Suzuki <koi...@gm...> wrote: > >> It is not correct. 1.0 and 1.1 are maintained. Fix of the issue may not be easy though. > > So, maintained, but no plan to release new versions? Sure, some bugs may be too much trouble for a maintained branch, but as Abbas says there are no plans to release new versions, it sounds an awful lot to me like no issues will be fixed, at least not in a release. > > Best, > > David > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > |
|
From: David E. W. <da...@ju...> - 2014-02-28 17:06:19
|
On Feb 27, 2014, at 10:51 PM, 鈴木 幸市 <ko...@in...> wrote: > Sorry, it has not been made open. Similar to PG, I’m planning to release 1.0.3 and 1.1.1 after 1.2GA is out. 1.2GA will be out when replicated table update/delete is fixed. Ah-ha, okay, thank you for the clarification. > I’m planning to include the following fixes in all the major/minor releases. > > 1. GTM Proxy fix to handle disconnection from backends: this caused “snapshot not available” error for heavy workloads. > 2. Fix restriction to use temporary objects. > 3. Fix statement cancellation error to improve random failure in the regression test. These sound like useful improvements. The temporary object fix will be particularly welcome. Can you tell me where savepoint support is in your roadmap? Thanks, David |
|
From: 鈴木 幸市 <ko...@in...> - 2014-03-03 00:59:49
|
Unfortunately, Savepoint is not in the roadmap yet. When a transaction needs new connection to other node, it must export existing Savepoints and also we need to handle unnamed savepoints as used in plpgsql. Temporary object fix was much simpler. In essence, I needed to change only three lines of code. Welcome if anybody can help to support the savepoint. Regards; --- Koichi Suzuki 2014/03/01 2:05、David E. Wheeler <da...@ju...> のメール： > On Feb 27, 2014, at 10:51 PM, 鈴木 幸市 <ko...@in...> wrote: > >> Sorry, it has not been made open. Similar to PG, I’m planning to release 1.0.3 and 1.1.1 after 1.2GA is out. 1.2GA will be out when replicated table update/delete is fixed. > > Ah-ha, okay, thank you for the clarification. > >> I’m planning to include the following fixes in all the major/minor releases. >> >> 1. GTM Proxy fix to handle disconnection from backends: this caused “snapshot not available” error for heavy workloads. >> 2. Fix restriction to use temporary objects. >> 3. Fix statement cancellation error to improve random failure in the regression test. > > These sound like useful improvements. The temporary object fix will be particularly welcome. > > Can you tell me where savepoint support is in your roadmap? > > Thanks, > > David > > |
×
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