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
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
(14) |
2
|
3
(4) |
4
(12) |
5
(14) |
6
|
|
7
(1) |
8
(7) |
9
(10) |
10
(7) |
11
(8) |
12
(6) |
13
|
|
14
(1) |
15
(3) |
16
(1) |
17
(8) |
18
(11) |
19
(3) |
20
|
|
21
(2) |
22
(9) |
23
(2) |
24
(14) |
25
(13) |
26
(1) |
27
|
|
28
|
29
(1) |
30
(11) |
|
|
|
|
|
From: Nikhil S. <ni...@st...> - 2013-04-24 18:16:00
|
Ok, This is not so straight forward. We cannot reset the sequence value in the GTM as is. We got to handle the case when the user can rollback the truncate operation in which case the old value should still hold. ISTM, we need to add handing code when the commit operation actually unlinks the corresponding underlying relfilenode for the earlier version of the sequence. Regards, Nikhils On Wed, Apr 24, 2013 at 7:34 PM, Ashutosh Bapat < ash...@en...> wrote: > Good, that works. This bug is causing testcase truncate to fail. > > > On Wed, Apr 24, 2013 at 6:53 PM, Nikhil Sontakke <ni...@st...>wrote: > >> Hi Ashutosh, >> >> By the EOW? >> >> Regards, >> Nikhils >> >> >> >> On Wed, Apr 24, 2013 at 6:49 PM, Ashutosh Bapat < >> ash...@en...> wrote: >> >>> Hi Nikhil, >>> Thanks for taking this up? >>> >>> By when do you think you can provide the patch? >>> >>> >>> On Wed, Apr 24, 2013 at 6:01 PM, Nikhil Sontakke <ni...@st...>wrote: >>> >>>> >>>> >>>> >>>> >>>>> ResetSequence(), the function being called from ExecuteTruncate() does >>>>> not send reset message to GTM. It applies sequence changes locally on the >>>>> coordinator, which is not enough. >>>>> >>>>> Can someone with relevant experience look into this problem and >>>>> provide a fix? >>>>> >>>>> I have attached the testcase and its output showing the bug. >>>>> >>>>> >>>> I guess setval() was handled but we forgot to handle reset sequence. I >>>> will take this up when I cleanup currval, nextval for negative sequences. >>>> >>>> Regards, >>>> Nikhils >>>> >>> >>> >>> >>> -- >>> Best Wishes, >>> Ashutosh Bapat >>> EntepriseDB Corporation >>> The Postgres Database Company >>> >> >> >> >> -- >> StormDB - http://www.stormdb.com >> The Database Cloud >> > > > > -- > Best Wishes, > Ashutosh Bapat > EntepriseDB Corporation > The Postgres Database Company > -- StormDB - http://www.stormdb.com The Database Cloud |
|
From: Abbas B. <abb...@en...> - 2013-04-24 17:42:11
|
Hi, The test was failing because ctid was being selected and was not being reset explicitly. SAVEPOINT is not implemented yet and the transaction fails because of that statement. Due to the failure / rollback the ctid remains incremented and that incremented value is dependent on cluster configuration. The solution is to explicitly reset ctid using truncate statement. -- *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: Abbas B. <abb...@en...> - 2013-04-24 17:29:16
|
Hi, The test was failing because some more tests are added in sql file. -- *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: Abbas B. <abb...@en...> - 2013-04-24 17:28:47
|
Hi, Test was failing because of some order by issues in COPY TO statements. -- *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: Abbas B. <abb...@en...> - 2013-04-24 17:28:08
|
Hi,
The test case fails if there is no primary node in the cluster. The
following test case was producing error.
CREATE TABLE tt_22 (a int, b int) distribute by replication;
INSERT INTO tt_22 VALUES (10);
In a four datanode cluster the following query plan was being produced.
explain verbose SELECT * FROM tt_22 FOR UPDATE;
QUERY PLAN
----------------------------------------------------------------------------
Data Node Scan on "__REMOTE_FQS_QUERY__" (cost=0.00..0.00 rows=0 width=0)
Output: tt_22.a, tt_22.b
Node/s: data_node_1, data_node_2, data_node_3, data_node_4
Remote query: SELECT a, b FROM tt_22 FOR UPDATE OF tt_22
(4 rows)
The reason was a missing else case in GetRelationNodes.
--
*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: Abbas B. <abb...@en...> - 2013-04-24 17:26:47
|
Hi, The test case was failing because of order by issues in copy. The solution is to use same data in both inserted rows, since it has nothing to do with the quoted name test. -- *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: Abbas B. <abb...@en...> - 2013-04-24 17:25:54
|
Hi, The test cases was failing for a four datanode cluster. The reason was that some tables were not created on a well defined datanode set. -- *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: Ashutosh B. <ash...@en...> - 2013-04-24 14:04:42
|
Good, that works. This bug is causing testcase truncate to fail. On Wed, Apr 24, 2013 at 6:53 PM, Nikhil Sontakke <ni...@st...>wrote: > Hi Ashutosh, > > By the EOW? > > Regards, > Nikhils > > > > On Wed, Apr 24, 2013 at 6:49 PM, Ashutosh Bapat < > ash...@en...> wrote: > >> Hi Nikhil, >> Thanks for taking this up? >> >> By when do you think you can provide the patch? >> >> >> On Wed, Apr 24, 2013 at 6:01 PM, Nikhil Sontakke <ni...@st...>wrote: >> >>> >>> >>> >>> >>>> ResetSequence(), the function being called from ExecuteTruncate() does >>>> not send reset message to GTM. It applies sequence changes locally on the >>>> coordinator, which is not enough. >>>> >>>> Can someone with relevant experience look into this problem and provide >>>> a fix? >>>> >>>> I have attached the testcase and its output showing the bug. >>>> >>>> >>> I guess setval() was handled but we forgot to handle reset sequence. I >>> will take this up when I cleanup currval, nextval for negative sequences. >>> >>> Regards, >>> Nikhils >>> >> >> >> >> -- >> Best Wishes, >> Ashutosh Bapat >> EntepriseDB Corporation >> The Postgres Database Company >> > > > > -- > StormDB - http://www.stormdb.com > The Database Cloud > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Postgres Database Company |
|
From: Nikhil S. <ni...@st...> - 2013-04-24 13:24:11
|
Hi Ashutosh, By the EOW? Regards, Nikhils On Wed, Apr 24, 2013 at 6:49 PM, Ashutosh Bapat < ash...@en...> wrote: > Hi Nikhil, > Thanks for taking this up? > > By when do you think you can provide the patch? > > > On Wed, Apr 24, 2013 at 6:01 PM, Nikhil Sontakke <ni...@st...>wrote: > >> >> >> >> >>> ResetSequence(), the function being called from ExecuteTruncate() does >>> not send reset message to GTM. It applies sequence changes locally on the >>> coordinator, which is not enough. >>> >>> Can someone with relevant experience look into this problem and provide >>> a fix? >>> >>> I have attached the testcase and its output showing the bug. >>> >>> >> I guess setval() was handled but we forgot to handle reset sequence. I >> will take this up when I cleanup currval, nextval for negative sequences. >> >> Regards, >> Nikhils >> > > > > -- > Best Wishes, > Ashutosh Bapat > EntepriseDB Corporation > The Postgres Database Company > -- StormDB - http://www.stormdb.com The Database Cloud |
|
From: Ashutosh B. <ash...@en...> - 2013-04-24 13:19:52
|
Hi Nikhil, Thanks for taking this up? By when do you think you can provide the patch? On Wed, Apr 24, 2013 at 6:01 PM, Nikhil Sontakke <ni...@st...>wrote: > > > > >> ResetSequence(), the function being called from ExecuteTruncate() does >> not send reset message to GTM. It applies sequence changes locally on the >> coordinator, which is not enough. >> >> Can someone with relevant experience look into this problem and provide a >> fix? >> >> I have attached the testcase and its output showing the bug. >> >> > I guess setval() was handled but we forgot to handle reset sequence. I > will take this up when I cleanup currval, nextval for negative sequences. > > Regards, > Nikhils > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Postgres Database Company |
|
From: Nikhil S. <ni...@st...> - 2013-04-24 12:32:08
|
> ResetSequence(), the function being called from ExecuteTruncate() does not > send reset message to GTM. It applies sequence changes locally on the > coordinator, which is not enough. > > Can someone with relevant experience look into this problem and provide a > fix? > > I have attached the testcase and its output showing the bug. > > I guess setval() was handled but we forgot to handle reset sequence. I will take this up when I cleanup currval, nextval for negative sequences. Regards, Nikhils |
|
From: Koichi S. <koi...@gm...> - 2013-04-24 02:35:24
|
It is system level error which may not happen so often in production. The
cause is failure in semaphore operation through Linux system call called
semop(). The failure may be called if you leave too many semaphore
unreleased in your system.
If you kill too many postmaster process of coordinator/datanode, they may
lose a chance to release these kernel resourcdes.
Please try ipcs -s (shows semaphore) and ipcs -m (shared memory) for all
the users in your system. It may help to see what's going on.
----------
Koichi Suzuki
2013/4/24 Venky Kandaswamy <ve...@ad...>
> Hi All,
>
> One of the datanodes (but not always the same node) gets a PANIC from
> the kernel and aborts. This causes the entire system to freeze. Cannot get
> any new connections and some transactions go into waiting. The message we
> are seeing in the logs are cryptic:
>
> {time user process message}
>
> 2013-04-23 11:42:49 PDT adchemy 17573 PANIC: semop(id=189366400) failed:
> Invalid argument
> 2013-04-23 11:42:49 PDT adchemy 17561 PANIC: semop(id=189366400) failed:
> Invalid argument
> 2013-04-23 11:42:50 PDT adchemy 17563 PANIC: semop(id=189366400) failed:
> Invalid argument
> 2013-04-23 11:42:50 PDT adchemy 17576 PANIC: semop(id=189366400) failed:
> Invalid argument
> 2013-04-23 12:08:31 PDT adchemy 17801 PANIC: semop(id=203915392) failed:
> Invalid argument
> 2013-04-23 12:08:31 PDT adchemy 17789 PANIC: semop(id=203915392) failed:
> Invalid argument
> 2013-04-23 12:08:31 PDT adchemy 17787 PANIC: semop(id=203915392) failed:
> Invalid argument
> 2013-04-23 12:08:33 PDT adchemy 17803 PANIC: semop(id=203915392) failed:
> Invalid argument
> 2013-04-23 12:08:33 PDT adchemy 17791 PANIC: semop(id=203915392) failed:
> Invalid argument
> 2013-04-23 12:09:31 PDT analytics 17812 PANIC: semop(id=203882623)
> failed: Invalid argument
> 2013-04-23 12:09:31 PDT adchemy 17797 PANIC: semop(id=203882623) failed:
> Invalid argument
> 2013-04-23 12:14:11 PDT analytics 17785 PANIC: semop(id=203882623)
> failed: Invalid argument
> 2013-04-23 12:14:11 PDT adchemy 17805 PANIC: semop(id=203882623) failed:
> Invalid argument
> 2013-04-23 12:16:11 PDT analytics 17783 PANIC: semop(id=203915392)
> failed: Invalid argument
> 2013-04-23 12:16:11 PDT analytics 17784 PANIC: semop(id=203915392)
> failed: Invalid argument
> 2013-04-23 12:16:11 PDT analytics 17786 PANIC: semop(id=203915392)
> failed: Invalid argument
> 2013-04-23 12:23:32 PDT analytics 17938 PANIC: semop(id=210141312)
> failed: Invalid argument
> 2013-04-23 12:23:32 PDT analytics 18544 PANIC: semop(id=210141312)
> failed: Invalid argument
> 2013-04-23 12:23:32 PDT analytics 17937 PANIC: semop(id=210141312)
> failed: Invalid argument
> 2013-04-23 12:23:32 PDT analytics 17951 PANIC: semop(id=210141312)
> failed: Invalid argument
>
> Any thoughts on why this might happen?
>
> ________________________________________
>
> Venky Kandaswamy
>
> Principal Engineer, Adchemy Inc.
>
> 925-200-7124
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>
|
2 messages has been excluded from this view by a project administrator.
