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: xiong w. <wan...@gm...> - 2010-11-16 03:09:17
|
Dears, Thanks for your suggestions. I should clarify my idea. 1)This patch is a temporary solution. It cann't really solve the problem raised by updating on a partition column until the measure that moving tuples from one node to another comes true. It just forbids users to update on a partition column. Therefore, I didn't consider too much because it will be deleted later. 2)The patch forbids update on partition column on coordinators. It has nothing to do with data nodes. If I misunderstand you, please let me know. Regards, Benny >Hi, >I'm curious about two issues on this patch. >1) Does it handle TOAST table correctly? >2) Does it handle SET clause such as SET key = key+1 ? Only a data node can determine if such UPDATE statement make rows invalid to stay in the data node. Unfortunately, data node is not equipped with distribution key. To handle this correctly, data node has to handle TOAST table as >mentioned in 1). >Regards; >--- >Koichi Suzuki (2010年11月15日 23:59), Mason Sharp wrote: > On 11/15/10 5:13 PM, mei le wrote: >> Dears, >> >> I am sorry. The bug#3107683.patch I commited before introduces a warning I didn't noticed. The enclosure is a new patch after I eliminated the warning. >> > Thanks. I just committed this and fixed a couple of other warnings that > we had. > > Regards, > > Mason >> Regards, >> >> Benny >> >> >> >> --- 10年11月12日，周五, Mason Sharp<mas...@en...> 写道： >> >> >> 发件人: Mason Sharp<mas...@en...> >> 主题: Fwd: [ postgres-xc-Bugs-3107683 ] UPDATE on partition column >> 收件人: "Postgres-XC Developers"<pos...@li...>, "mei le"<lem...@ya...> >> 日期: 2010年11月12日,周五,上午10:34 >> >> >> Benny, >> >> I thought this might be one you might be interested in working on, too, if you have time. >> >> You could validate the update statement in pgxc_planner() if it is on a partitioned table. >> >> Thanks, >> >> Mason >> >> -------- Original Message -------- >> >> >> >> Subject: >> [ postgres-xc-Bugs-3107683 ] UPDATE on partition column >> >> Date: >> Fri, 12 Nov 2010 02:29:56 +0000 >> >> From: >> SourceForge.net<no...@so...> >> >> To: >> no...@so... >> >> Bugs item #3107683, was opened at 2010-11-11 21:29 >> Message generated for change (Tracker Item Submitted) made by mason_s >> You can respond by visiting: >> https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227 >> >> Please note that this message will contain a full copy of the comment thread, >> including the initial issue submission, for this request, >> not just the latest update. >> Category: Database Server >> Group: None >> Status: Open >> Resolution: None >> Priority: 6 >> Private: No >> Submitted By: mason_s (mason_s) >> Assigned to: Nobody/Anonymous (nobody) >> Summary: UPDATE on partition column >> >> Initial Comment: >> Until we support moving tuples from one node to another when the partition column of a table is updated, we should at least block this from happening. At the moment you can update it, and bad things can start happening as a result. >> >> ---------------------------------------------------------------------- >> >> You can respond by visiting: >> https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227 >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Centralized Desktop Delivery: Dell and VMware Reference Architecture >> Simplifying enterprise desktop deployment and management using >> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end >> client virtualization framework. Read more! >> http://p.sf.net/sfu/dell-eql-dev2dev >> >> >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> > > > -- > Mason Sharp > EnterpriseDB Corporation > The Enterprise Postgres Company > > > 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: Koichi S. <ko...@in...> - 2010-11-16 00:48:09
|
Hi, I'm curious about two issues on this patch. 1) Does it handle TOAST table correctly? 2) Does it handle SET clause such as SET key = key+1 ? Only a data node can determine if such UPDATE statement make rows invalid to stay in the data node. Unfortunately, data node is not equipped with distribution key. To handle this correctly, data node has to handle TOAST table as mentioned in 1). Regards; --- Koichi Suzuki (2010年11月15日 23:59), Mason Sharp wrote: > On 11/15/10 5:13 PM, mei le wrote: >> Dears, >> >> I am sorry. The bug#3107683.patch I commited before introduces a warning I didn't noticed. The enclosure is a new patch after I eliminated the warning. >> > Thanks. I just committed this and fixed a couple of other warnings that > we had. > > Regards, > > Mason >> Regards, >> >> Benny >> >> >> >> --- 10年11月12日，周五, Mason Sharp<mas...@en...> 写道： >> >> >> 发件人: Mason Sharp<mas...@en...> >> 主题: Fwd: [ postgres-xc-Bugs-3107683 ] UPDATE on partition column >> 收件人: "Postgres-XC Developers"<pos...@li...>, "mei le"<lem...@ya...> >> 日期: 2010年11月12日,周五,上午10:34 >> >> >> Benny, >> >> I thought this might be one you might be interested in working on, too, if you have time. >> >> You could validate the update statement in pgxc_planner() if it is on a partitioned table. >> >> Thanks, >> >> Mason >> >> -------- Original Message -------- >> >> >> >> Subject: >> [ postgres-xc-Bugs-3107683 ] UPDATE on partition column >> >> Date: >> Fri, 12 Nov 2010 02:29:56 +0000 >> >> From: >> SourceForge.net<no...@so...> >> >> To: >> no...@so... >> >> Bugs item #3107683, was opened at 2010-11-11 21:29 >> Message generated for change (Tracker Item Submitted) made by mason_s >> You can respond by visiting: >> https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227 >> >> Please note that this message will contain a full copy of the comment thread, >> including the initial issue submission, for this request, >> not just the latest update. >> Category: Database Server >> Group: None >> Status: Open >> Resolution: None >> Priority: 6 >> Private: No >> Submitted By: mason_s (mason_s) >> Assigned to: Nobody/Anonymous (nobody) >> Summary: UPDATE on partition column >> >> Initial Comment: >> Until we support moving tuples from one node to another when the partition column of a table is updated, we should at least block this from happening. At the moment you can update it, and bad things can start happening as a result. >> >> ---------------------------------------------------------------------- >> >> You can respond by visiting: >> https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227 >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Centralized Desktop Delivery: Dell and VMware Reference Architecture >> Simplifying enterprise desktop deployment and management using >> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end >> client virtualization framework. Read more! >> http://p.sf.net/sfu/dell-eql-dev2dev >> >> >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> > > > -- > Mason Sharp > EnterpriseDB Corporation > The Enterprise Postgres Company > > > 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. > > > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > > > > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: Mason S. <mas...@en...> - 2010-11-15 14:59:59
|
On 11/15/10 5:13 PM, mei le wrote: > Dears, > > I am sorry. The bug#3107683.patch I commited before introduces a warning I didn't noticed. The enclosure is a new patch after I eliminated the warning. > Thanks. I just committed this and fixed a couple of other warnings that we had. Regards, Mason > Regards, > > Benny > > > > --- 10年11月12日，周五, Mason Sharp <mas...@en...> 写道： > > > 发件人: Mason Sharp <mas...@en...> > 主题: Fwd: [ postgres-xc-Bugs-3107683 ] UPDATE on partition column > 收件人: "Postgres-XC Developers" <pos...@li...>, "mei le" <lem...@ya...> > 日期: 2010年11月12日,周五,上午10:34 > > > Benny, > > I thought this might be one you might be interested in working on, too, if you have time. > > You could validate the update statement in pgxc_planner() if it is on a partitioned table. > > Thanks, > > Mason > > -------- Original Message -------- > > > > Subject: > [ postgres-xc-Bugs-3107683 ] UPDATE on partition column > > Date: > Fri, 12 Nov 2010 02:29:56 +0000 > > From: > SourceForge.net <no...@so...> > > To: > no...@so... > > Bugs item #3107683, was opened at 2010-11-11 21:29 > Message generated for change (Tracker Item Submitted) made by mason_s > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227 > > Please note that this message will contain a full copy of the comment thread, > including the initial issue submission, for this request, > not just the latest update. > Category: Database Server > Group: None > Status: Open > Resolution: None > Priority: 6 > Private: No > Submitted By: mason_s (mason_s) > Assigned to: Nobody/Anonymous (nobody) > Summary: UPDATE on partition column > > Initial Comment: > Until we support moving tuples from one node to another when the partition column of a table is updated, we should at least block this from happening. At the moment you can update it, and bad things can start happening as a result. > > ---------------------------------------------------------------------- > > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227 > > > > > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > > > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- Mason Sharp EnterpriseDB Corporation The Enterprise Postgres Company 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: mei le <lem...@ya...> - 2010-11-15 08:13:17
|
Dears,
I am sorry. The bug#3107683.patch I commited before introduces a warning I didn't noticed. The enclosure is a new patch after I eliminated the warning.
Regards,
Benny
--- 10年11月12日，周五, Mason Sharp <mas...@en...> 写道：
发件人: Mason Sharp <mas...@en...>
主题: Fwd: [ postgres-xc-Bugs-3107683 ] UPDATE on partition column
收件人: "Postgres-XC Developers" <pos...@li...>, "mei le" <lem...@ya...>
日期: 2010年11月12日,周五,上午10:34
Benny,
I thought this might be one you might be interested in working on, too, if you have time.
You could validate the update statement in pgxc_planner() if it is on a partitioned table.
Thanks,
Mason
-------- Original Message --------
Subject:
[ postgres-xc-Bugs-3107683 ] UPDATE on partition column
Date:
Fri, 12 Nov 2010 02:29:56 +0000
From:
SourceForge.net <no...@so...>
To:
no...@so...
Bugs item #3107683, was opened at 2010-11-11 21:29
Message generated for change (Tracker Item Submitted) made by mason_s
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database Server
Group: None
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: mason_s (mason_s)
Assigned to: Nobody/Anonymous (nobody)
Summary: UPDATE on partition column
Initial Comment:
Until we support moving tuples from one node to another when the partition column of a table is updated, we should at least block this from happening. At the moment you can update it, and bad things can start happening as a result.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227
|
|
From: mei le <lem...@ya...> - 2010-11-15 05:55:02
|
Dears,
This patch forbids users to update partition column of a table.
Your suggestions will be appreciated.
Regards,
Benny
--- 10年11月12日，周五, Mason Sharp <mas...@en...> 写道：
发件人: Mason Sharp <mas...@en...>
主题: Fwd: [ postgres-xc-Bugs-3107683 ] UPDATE on partition column
收件人: "Postgres-XC Developers" <pos...@li...>, "mei le" <lem...@ya...>
日期: 2010年11月12日,周五,上午10:34
Benny,
I thought this might be one you might be interested in working on, too, if you have time.
You could validate the update statement in pgxc_planner() if it is on a partitioned table.
Thanks,
Mason
-------- Original Message --------
Subject:
[ postgres-xc-Bugs-3107683 ] UPDATE on partition column
Date:
Fri, 12 Nov 2010 02:29:56 +0000
From:
SourceForge.net <no...@so...>
To:
no...@so...
Bugs item #3107683, was opened at 2010-11-11 21:29
Message generated for change (Tracker Item Submitted) made by mason_s
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database Server
Group: None
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: mason_s (mason_s)
Assigned to: Nobody/Anonymous (nobody)
Summary: UPDATE on partition column
Initial Comment:
Until we support moving tuples from one node to another when the partition column of a table is updated, we should at least block this from happening. At the moment you can update it, and bad things can start happening as a result.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227
|
|
From: Mason S. <mas...@en...> - 2010-11-13 23:48:50
|
On 11/12/10 4:53 AM, mei le wrote: > Dears, > > Today, I created a function which inserts a value into a table. When I call the function, it doesn't work. I don't know whether PGXC supports Procedure or Function? > > If not, do we have a plan to develop it? I consider it must be complicated. I don't see anything about it from website and documents. > Functions using parameters that end up in SQL statements use prepared statements internally. Support for this is currently being worked on, and you can expect some initial support by the end of the year. Regards, Mason > Your reply will be appreciated. > > Regards, > Benny > > > > > > > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- Mason Sharp EnterpriseDB Corporation The Enterprise Postgres Company 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: mei le <lem...@ya...> - 2010-11-12 09:53:33
|
Dears,
Today, I created a function which inserts a value into a table. When I call the function, it doesn't work. I don't know whether PGXC supports Procedure or Function?
If not, do we have a plan to develop it? I consider it must be complicated. I don't see anything about it from website and documents.
Your reply will be appreciated.
Regards,
Benny
|
|
From: mei le <lem...@ya...> - 2010-11-12 06:55:14
|
Dears,
Thanks for your modifications and comments on this patch. I am sorry for my mistakes. I will be more careful during later work.
I checked the patch and tested it in our project. The result proved that it does work well.
Thanks again.
Regards,
Benny
--- 10年11月12日，周五, Michael Paquier <mic...@gm...> 写道：
发件人: Michael Paquier <mic...@gm...>
主题: Re: [Postgres-xc-developers] Patch for bug#3013984: Sequence scope
收件人: "mei le" <lem...@ya...>
抄送: "pg" <pos...@li...>
日期: 2010年11月12日,周五,下午12:23
Hi Benny,
I had a look at your patch,
and it is really a nice feature you implemented.
With this functionnality, it is possible to drop sequences on GTM in a very smooth way when a database is dropped.
I have a couple of comments about it though.
1) in gtm_seq.c, function seq_start_with_nsp
You make a memory compare that will always return a true result because you compare the same string.
return ((memcmp(nsp->gsk_key, nsp->gsk_key, nsp->gsk_keylen) == 0)
&& (seq->gsk_key[nsp->gsk_keylen] == '.'));
I believe this is the right code:
return ((memcmp(nsp->gsk_key, seq->gsk_key, nsp->gsk_keylen) == 0)
&& (seq->gsk_key[nsp->gsk_keylen] == '.'));
2) in gtm_seq.c, function GTM_RmSeqWithNsp
When you encounter a sequence that is used by another process, you mark it for deletion and then you exit the process,
letting perhaps a lot of sequences not dropped.
I think priority should be given to deletion, as DROP DATABASE has to be forced.
Btw, a busy sequence cannot basically be found because that would mean that an instance is still using the database,
and in this case database drop is not possible.
3) in gtm_c.h, about the message type definition.
I made a modification in message type so as not to use a unique character.
Using an enumeration (typedef enum) makes it more consistent with Postgres-xc code, and it makes code maintenance easier.
4) Also I notice a couple of typo problems, take care when you use spaces and tabs!
I corrected those points above in the patch attached.
I also changed a couple of function names to make it clearer.
You should check it and make a couple of additional tests also.
Perhaps you have additional ideas about this implementation, don't hesitate to share what you think.
Regards,
--
Michael Paquier
http://michaelpq.users.sourceforge.net
|
|
From: Michael P. <mic...@gm...> - 2010-11-12 04:24:05
|
Hi Benny,
I had a look at your patch,
and it is really a nice feature you implemented.
With this functionnality, it is possible to drop sequences on GTM in a very
smooth way when a database is dropped.
I have a couple of comments about it though.
1) in gtm_seq.c, function seq_start_with_nsp
You make a memory compare that will always return a true result because you
compare the same string.
return ((memcmp(nsp->gsk_key, nsp->gsk_key, nsp->gsk_keylen) ==
0)
&& (seq->gsk_key[nsp->gsk_keylen] == '.'));
I believe this is the right code:
return ((memcmp(nsp->gsk_key, seq->gsk_key, nsp->gsk_keylen) ==
0)
&& (seq->gsk_key[nsp->gsk_keylen] == '.'));
2) in gtm_seq.c, function GTM_RmSeqWithNsp
When you encounter a sequence that is used by another process, you mark it
for deletion and then you exit the process,
letting perhaps a lot of sequences not dropped.
I think priority should be given to deletion, as DROP DATABASE has to be
forced.
Btw, a busy sequence cannot basically be found because that would mean that
an instance is still using the database,
and in this case database drop is not possible.
3) in gtm_c.h, about the message type definition.
I made a modification in message type so as not to use a unique character.
Using an enumeration (typedef enum) makes it more consistent with
Postgres-xc code, and it makes code maintenance easier.
4) Also I notice a couple of typo problems, take care when you use spaces
and tabs!
I corrected those points above in the patch attached.
I also changed a couple of function names to make it clearer.
You should check it and make a couple of additional tests also.
Perhaps you have additional ideas about this implementation, don't hesitate
to share what you think.
Regards,
--
Michael Paquier
http://michaelpq.users.sourceforge.net
|
|
From: Mason S. <mas...@en...> - 2010-11-12 02:34:16
|
Benny, I thought this might be one you might be interested in working on, too, if you have time. You could validate the update statement in pgxc_planner() if it is on a partitioned table. Thanks, Mason -------- Original Message -------- Subject: [ postgres-xc-Bugs-3107683 ] UPDATE on partition column Date: Fri, 12 Nov 2010 02:29:56 +0000 From: SourceForge.net <no...@so...> To: no...@so... Bugs item #3107683, was opened at 2010-11-11 21:29 Message generated for change (Tracker Item Submitted) made by mason_s You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Server Group: None Status: Open Resolution: None Priority: 6 Private: No Submitted By: mason_s (mason_s) Assigned to: Nobody/Anonymous (nobody) Summary: UPDATE on partition column Initial Comment: Until we support moving tuples from one node to another when the partition column of a table is updated, we should at least block this from happening. At the moment you can update it, and bad things can start happening as a result. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227 |
|
From: Koichi S. <ko...@in...> - 2010-11-09 00:11:19
|
Mason-san; Thanks for the reply. --- Koichi (2010年11月09日 01:30), Mason Sharp wrote: > On 11/8/10 5:13 AM, mei le wrote: >> Dears, >> the steps as follows: >> postgres=# create database dbt1; >> CREATE DATABASE >> postgres=# \c dbt1 >> psql (8.4.3) >> You are now connected to database "dbt1". >> dbt1=# create table t(a int); >> CREATE TABLE >> dbt1=# \c postgres >> psql (8.4.3) >> You are now connected to database "postgres". >> postgres=# drop database dbt1; >> ERROR: database "dbt1" is being accessed by other users >> DETAIL: There are 1 other session(s) using the database. >> In addition,it's ok to drop databse if I didn't create any object in >> database dbt1. >> regards, >> Benny >> >> > > Thanks, this is a known issue. The issue is that the pooler is holding > on to the connections. Michael is doing some work right now to clean > pooler connections. I think it should get committed sometime in the next > week or so. > > Thanks, > > Mason > >> >> ------------------------------------------------------------------------------ >> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> David G. Thomson, author of the best-selling book "Blueprint to a >> Billion" shares his insights and actions to help propel your >> business during the next growth cycle. Listen Now! >> http://p.sf.net/sfu/SAP-dev2dev >> >> >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> > > > -- > Mason Sharp > EnterpriseDB Corporation > The Enterprise Postgres Company > > > 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. > > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > > > > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: Mason S. <mas...@en...> - 2010-11-08 16:31:40
|
On 11/8/10 5:13 AM, mei le wrote: > Dears, > the steps as follows: > postgres=# create database dbt1; > CREATE DATABASE > postgres=# \c dbt1 > psql (8.4.3) > You are now connected to database "dbt1". > dbt1=# create table t(a int); > CREATE TABLE > dbt1=# \c postgres > psql (8.4.3) > You are now connected to database "postgres". > postgres=# drop database dbt1; > ERROR: database "dbt1" is being accessed by other users > DETAIL: There are 1 other session(s) using the database. > In addition,it's ok to drop databse if I didn't create any object in > database dbt1. > > regards, > > Benny > > Thanks, this is a known issue. The issue is that the pooler is holding on to the connections. Michael is doing some work right now to clean pooler connections. I think it should get committed sometime in the next week or so. Thanks, Mason > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > > > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- Mason Sharp EnterpriseDB Corporation The Enterprise Postgres Company 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: mei le <lem...@ya...> - 2010-11-08 10:13:12
|
Dears,
the steps as follows:
postgres=# create database dbt1;
CREATE DATABASE
postgres=# \c dbt1
psql (8.4.3)
You are now connected to database "dbt1".
dbt1=# create table t(a int);
CREATE TABLE
dbt1=# \c postgres
psql (8.4.3)
You are now connected to database "postgres".
postgres=# drop database dbt1;
ERROR: database "dbt1" is being accessed by other users
DETAIL: There are 1 other session(s) using the database.
In addition,it's ok to drop databse if I didn't create any object in database dbt1.
regards,
Benny
|
|
From: mei le <lem...@ya...> - 2010-11-04 03:44:53
|
Dears,
steps as follows:
1.create table test(a int);
2.insert into test(a) values(1) returning a;
The result on pgxc version 0.9.3 is:
template1=# insert into test(a) values(1) returning a;
INSERT 0 2
Actually, only one value is inserted.
The expected result is:
template1=# insert into test(a) values(1) returning a;
a
---
1
(1 row)
INSERT 0 1
Best regards,
Benny
|
|
From: Koichi S. <koi...@gm...> - 2010-10-29 06:27:09
|
Postgres-XC development team is pleased to announce that Postgres-XC Version 0.9.3 is now available. Major additional features include: Transparent DDL. Now DDL is automatically propagated to all the coordinators and data nodes. General SQL support: Statements may include cross node joins. Extended protocol support for libpq: This is needed to use Postgres-XC from Java. Cursor support: This is also needed by Java and other languages. Global Timestamp: Timestamps are now supplied by GTM. This version includes many bug fixes and is much more stable than previous ones. We've tested DBT-1 benchmark for one week with 90% of full load. The test ran stably without any error in DBT-1. You can download the release from Postgres-XC project page: https://sourceforge.net/projects/postgres-xc/ General information is available in Project page: http://postgres-xc.sourceforge.net/ ---------- Postgres-XC Development Team Koichi Suzuki |
|
From: Mason S. <mas...@en...> - 2010-10-22 18:57:10
|
> > Enclosure is my patch for bug#3010262. Your suggestions will be > appreciated. > > Truely, > > Benny > > > Thanks, Benny. In looking at the patch, I am guessing the main issue you fixed was that it will create an additional create index command, and that we do not want to send it down to the data nodes since one already ran as part of the create table. I think we should try and avoid modifying the existing PostgreSQL function parameter list like that for transformIndexConstraints() if reasonably (stress: reasonably) possible to make merging and maintenance of PostgreSQL easier. Can CreateStmtContext.isalter be used instead? Can it even be used in utility.c instead of isFromCreateStmt? Thanks, Mason > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps& games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > > > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- Mason Sharp EnterpriseDB Corporation The Enterprise Postgres Company 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: Mason S. <mas...@en...> - 2010-10-22 14:24:18
|
Benny, Just to provide more background, PostgreSQL uses MVCC, so transaction ids (XID or GXID) are important for determining what is visible within the database. These IDs are obtained from GTM. If in the cluster these advance and GTM is restarted with a low XID, then your previous work will not be visible. It is important to start it with at least the last id. As Koichi mentioned, if you stop gracefully it will write the current value in a file and on restart will read this value (unless overridden by a passed in value). If GTM crashed and you restart, you will need to manually pass in a high value. As Koichi also mentioned, we are currently working on this to recover this value properly. Regards, Mason On 10/22/10 3:26 AM, Koichi Suzuki wrote: > How did you stop and restart GTM? > > If you stop gtm gracefully, it will restart to start with next GXID. > If GTM crashed and you restart, you may need to specify GXID to start with. > > Safer GTM recovery and restart will be implemented by the end of this year. > > Regards; > --- > Koichi Suzuki > > (2010年10月22日 15:59), mei le wrote: > >> Deras, >> When I restart the GTM, all my tables disppeare. I don't know why. Is is >> a problem or was what I did wrong? >> Your reply will be appreciated. >> Truely, >> Benny >> >> >> >> >> ------------------------------------------------------------------------------ >> Nokia and AT&T present the 2010 Calling All Innovators-North America contest >> Create new apps& games for the Nokia N8 for consumers in U.S. and Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store >> http://p.sf.net/sfu/nokia-dev2dev >> >> >> >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps& games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- Mason Sharp EnterpriseDB Corporation The Enterprise Postgres Company 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: Koichi S. <ko...@in...> - 2010-10-22 07:24:30
|
How did you stop and restart GTM? If you stop gtm gracefully, it will restart to start with next GXID. If GTM crashed and you restart, you may need to specify GXID to start with. Safer GTM recovery and restart will be implemented by the end of this year. Regards; --- Koichi Suzuki (2010年10月22日 15:59), mei le wrote: > Deras, > When I restart the GTM, all my tables disppeare. I don't know why. Is is > a problem or was what I did wrong? > Your reply will be appreciated. > Truely, > Benny > > > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps& games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > > > > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: mei le <lem...@ya...> - 2010-10-22 06:59:59
|
Deras,
When I restart the GTM, all my tables disppeare. I don't know why. Is is a problem or was what I did wrong?
Your reply will be appreciated.
Truely,
Benny
|
|
From: Mason S. <mas...@en...> - 2010-10-20 15:27:16
|
Benny, Thanks for reporting this. It turns out this is working in the PGXC-sqlmed branch in the git repository. This branch will be merged into HEAD sometime soon and the issue will no longer occur. In general there are some improvements we should do for cartesian products. Thanks, Mason On 10/19/10 9:49 PM, Koichi Suzuki wrote: > Hi, > > I'm afraid "from tt1, tt2" causes curtesian product of two tables, which > may not be supported at present version. > I suppose "select count(*) from tt1;" and "select count(*) from tt2;" > will run without problems. > > Cheers; > --- > Koichi > > (2010年10月20日 10:37), mei le wrote: > >> Dears, >> steps: >> 1.create table tt1(a int); >> 2.create table tt2(a int); >> 3.insert into tt1 values(1);insert into tt2 values(1); >> 4.select count(*) from tt1,tt2; >> template1=# select count(*) from tt1,tt2; >> server closed the connection unexpectedly >> This probably means the server terminated abnormally >> before or while processing the request. >> The connection to the server was lost. Attempting reset: LOG: server >> process (PID 2239) was terminated by signal 11: Segmentation fault >> LOG: terminating any other active server processes >> LOG: all server processes terminated; reinitializing >> LOG: database system was interrupted; last known up at 2010-10-20 >> 09:36:17 CST >> LOG: database system was not properly shut down; automatic recovery in >> progress >> FATAL: failed to connect to pool manager: Connection refused >> Failed. >> !> LOG: record with zero length at 0/4DA980 >> LOG: redo is not required >> Using aggregate functions on mutiple tables join will all cause such a >> problem. >> Benny >> >> >> >> >> ------------------------------------------------------------------------------ >> Download new Adobe(R) Flash(R) Builder(TM) 4 >> The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly >> Flex(R) Builder(TM)) enable the development of rich applications that run >> across multiple browsers and platforms. Download your free trials today! >> http://p.sf.net/sfu/adobe-dev2dev >> >> >> >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- Mason Sharp EnterpriseDB Corporation The Enterprise Postgres Company 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: Koichi S. <ko...@in...> - 2010-10-20 01:48:14
|
Hi, I'm afraid "from tt1, tt2" causes curtesian product of two tables, which may not be supported at present version. I suppose "select count(*) from tt1;" and "select count(*) from tt2;" will run without problems. Cheers; --- Koichi (2010年10月20日 10:37), mei le wrote: > Dears, > steps: > 1.create table tt1(a int); > 2.create table tt2(a int); > 3.insert into tt1 values(1);insert into tt2 values(1); > 4.select count(*) from tt1,tt2; > template1=# select count(*) from tt1,tt2; > server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > The connection to the server was lost. Attempting reset: LOG: server > process (PID 2239) was terminated by signal 11: Segmentation fault > LOG: terminating any other active server processes > LOG: all server processes terminated; reinitializing > LOG: database system was interrupted; last known up at 2010-10-20 > 09:36:17 CST > LOG: database system was not properly shut down; automatic recovery in > progress > FATAL: failed to connect to pool manager: Connection refused > Failed. > !> LOG: record with zero length at 0/4DA980 > LOG: redo is not required > Using aggregate functions on mutiple tables join will all cause such a > problem. > Benny > > > > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > > > > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: mei le <lem...@ya...> - 2010-10-20 01:37:51
|
Dears,
steps:
1.create table tt1(a int);
2.create table tt2(a int);
3.insert into tt1 values(1);insert into tt2 values(1);
4.select count(*) from tt1,tt2;
template1=# select count(*) from tt1,tt2;
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: LOG: server process (PID 2239) was terminated by signal 11: Segmentation fault
LOG: terminating any other active server processes
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2010-10-20 09:36:17 CST
LOG: database system was not properly shut down; automatic recovery in progress
FATAL: failed to connect to pool manager: Connection refused
Failed.
!> LOG: record with zero length at 0/4DA980
LOG: redo is not required
Using aggregate functions on mutiple tables join will all cause such a problem.
Benny
|
|
From: mei le <lem...@ya...> - 2010-10-19 06:39:09
|
Dears,
Maybe a bug. My test environment:two coordinators, two datanodes.The steps are described as follows:
1. create table tt(a int);
2. alter table tt add constraint pk primary key(a);
3. insert into tt values(8);
4. insert into tt values(8);
when execute step 4, something happened.
coordinator log:
template1=# insert into tt values(8);
INSERT 0 1
template1=# insert into tt values(8);
WARNING: unexpected EOF on datanode connection
ERROR: Failed to read response from data nodes
STATEMENT: insert into tt values(8);
WARNING: unexpected EOF on datanode connection
WARNING: unexpected EOF on datanode connection
WARNING: unexpected EOF on datanode connection
ERROR: Failed to read response from data nodes
template1=# LOG: failed to connect to data node
LOG: failed to connect to data node
Two datanodes' logs are described respectively.
local one:
LOG: statement: BEGIN
LOG: statement: insert into tt values(8);
LOG: statement: PREPARE TRANSACTION 'T116'
LOG: statement: COMMIT PREPARED 'T116'
LOG: statement: BEGIN
LOG: statement: insert into tt values(8);
ERROR: duplicate key value violates unique constraint "pk"
STATEMENT: insert into tt values(8);
PANIC: cannot abort transaction 118, it was already committed
LOG: server process (PID 1374) was terminated by signal 6: Aborted
LOG: terminating any other active server processes
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2010-10-19 14:30:31 CST
LOG: database system was not properly shut down; automatic recovery in progress
The session started: 1376
FATAL: the database system is in recovery mode
LOG: redo starts at 0/4BC07C
LOG: record with zero length at 0/4BC408
LOG: redo done at 0/4BC3DC
LOG: last completed transaction was at log time 2021-08-06 21:02:14.101545+08
LOG: autovacuum launcher started
LOG: database system is ready to accept connections
The remote datanode log:
LOG: statement: BEGIN
LOG: statement: insert into tt values(8);
LOG: statement: PREPARE TRANSACTION 'T116'
LOG: statement: COMMIT PREPARED 'T116'
LOG: statement: BEGIN
LOG: statement: insert into tt values(8);
LOG: statement: ROLLBACK
PANIC: cannot abort transaction 118, it was already committed
STATEMENT: ROLLBACK
LOG: server process (PID 28899) was terminated by signal 6: Aborted
LOG: terminating any other active server processes
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2010-10-19 14:29:49 CST
LOG: database system was not properly shut down; automatic recovery in progress
The session started: 28901
FATAL: the database system is in recovery mode
LOG: redo starts at 0/712738
LOG: record with zero length at 0/712A44
LOG: redo done at 0/712A18
LOG: last completed transaction was at log time 2021-08-06 21:01:31.960109+08
LOG: autovacuum launcher started
LOG: database system is ready to accept connections
Truely,
Benny
|
|
From: Mason S. <mas...@en...> - 2010-10-18 04:51:57
|
Hi Benny, This was one of the items on the bug list I had previously sent to you. Thanks, Mason Sent from my IPhone On Oct 17, 2010, at 10:49 PM, mei le <lem...@ya...> wrote: > Dears, > > One bug occured. > > template1=# create table t2(a int primary key); > server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > The connection to the server was lost. Attempting reset: LOG: server process (PID 2429) was terminated by signal 11: Segmentation fault > LOG: terminating any other active server processes > FATAL: failed to connect to pool manager: Connection refused > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and repeat your command. > Failed. > !> > > > Truely, > Benny > > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: mei le <lem...@ya...> - 2010-10-18 02:49:52
|
Dears,
One bug occured.
template1=# create table t2(a int primary key);
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: LOG: server process (PID 2429) was terminated by signal 11: Segmentation fault
LOG: terminating any other active server processes
FATAL: failed to connect to pool manager: Connection refused
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
Failed.
!>
Truely,
Benny
|
261 messages has been excluded from this view by a project administrator.
