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
(11) |
2
(7) |
3
(6) |
4
|
|
5
|
6
(1) |
7
(2) |
8
(2) |
9
(6) |
10
(2) |
11
|
|
12
(1) |
13
(6) |
14
(5) |
15
(4) |
16
(5) |
17
(4) |
18
|
|
19
|
20
(1) |
21
(3) |
22
(2) |
23
(1) |
24
|
25
|
|
26
|
27
(5) |
28
|
29
|
30
|
31
|
|
|
From: Andrei.Martsinchyk <and...@en...> - 2010-12-03 18:10:55
|
Mason, 2010/12/3 Mason Sharp <mas...@en...>: > > > > Sent from my IPhone > > On Dec 3, 2010, at 5:31 PM, "Andrei.Martsinchyk" <and...@en...> wrote: > >> Mason, >> >> 2010/12/3 Mason Sharp <mas...@en...>: >>> On 12/1/10 1:53 PM, Andrei.Martsinchyk wrote: >>>> >>>> Hi Benny, >>>> >>>> Thanks for pointing this out. I tested with a program using Postgres C >>>> library and extended query protocol. >>>> For you and anyone else who want to test I am attaching the test >>>> program and simple Makefile. >>>> I fixed the segmentation fault (updated patch is attached), but >>>> anyway, PREPARE / EXECUTE commands do not work properly. >>>> >>> >>> It looks like it is still not quite right: >>> >>> >>> mds1=# create table mytab (col1 int, col2 int); >>> CREATE TABLE >>> mds1=# prepare p (int, int) AS INSERT INTO mytab VALUES ($1, $2); >>> PREPARE >>> mds1=# execute p (1,2); >>> INSERT 0 1 >>> mds1=# select * from mytab; >>> col1 | col2 >>> ------+------ >>> (0 rows) >>> >>> It does not find the row that should have been inserted. >>> >> >> Yes, I mentioned the PREPARE command does not work properly. >> In this particular case it is inserting row into Coordinator database >> and not visible for select. >> > > Oh. So, only SELECT is currently handled? > Some SELECTs work properly, not all. >>> Also, one other question- the session seems to retain the fact that there >>> are associated prepared statements. Does that mean that the pooler will not >>> put these back in the pool until all are deallocated? >>> >> >> Coordinator does not prepare statements on datanodes, so connection >> can be released at the transaction end. > > It converts it into a simple statement? I think we need to support prepare and execute on the data nodes for performance. > It does not seem straightforward. Prepared statement is a cached plan, and it is cached on coordinator. If the plan contains multiple RemoteQuery nodes we should prepare each, and should not release these until all they are closed. We should be holding the data node connections all this time. >> >>> On a related note, for the WITH HOLD cursors you implemented, did you also >>> do something to hold on to the connections? >>> >> >> I did not implement WITH HOLD. > > Let me retest this, and look at old emails later when back at my laptop. > I remember someone told me it works, but I never tested, and never did anything to handle it. > Mason >> >>> Thanks, >>> >>> Mason >>> >>> >>> >>> >>> 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. >>> >>> >> >> >> >> -- >> Andrei Martsinchyk >> >> EntepriseDB Corporation >> The Enterprise Postgres Company >> >> 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. > -- Andrei Martsinchyk EntepriseDB Corporation The Enterprise Postgres Company 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: Mason S. <mas...@en...> - 2010-12-03 17:19:35
|
Sent from my IPhone On Dec 3, 2010, at 5:31 PM, "Andrei.Martsinchyk" <and...@en...> wrote: > Mason, > > 2010/12/3 Mason Sharp <mas...@en...>: >> On 12/1/10 1:53 PM, Andrei.Martsinchyk wrote: >>> >>> Hi Benny, >>> >>> Thanks for pointing this out. I tested with a program using Postgres C >>> library and extended query protocol. >>> For you and anyone else who want to test I am attaching the test >>> program and simple Makefile. >>> I fixed the segmentation fault (updated patch is attached), but >>> anyway, PREPARE / EXECUTE commands do not work properly. >>> >> >> It looks like it is still not quite right: >> >> >> mds1=# create table mytab (col1 int, col2 int); >> CREATE TABLE >> mds1=# prepare p (int, int) AS INSERT INTO mytab VALUES ($1, $2); >> PREPARE >> mds1=# execute p (1,2); >> INSERT 0 1 >> mds1=# select * from mytab; >> col1 | col2 >> ------+------ >> (0 rows) >> >> It does not find the row that should have been inserted. >> > > Yes, I mentioned the PREPARE command does not work properly. > In this particular case it is inserting row into Coordinator database > and not visible for select. > Oh. So, only SELECT is currently handled? >> Also, one other question- the session seems to retain the fact that there >> are associated prepared statements. Does that mean that the pooler will not >> put these back in the pool until all are deallocated? >> > > Coordinator does not prepare statements on datanodes, so connection > can be released at the transaction end. It converts it into a simple statement? I think we need to support prepare and execute on the data nodes for performance. > >> On a related note, for the WITH HOLD cursors you implemented, did you also >> do something to hold on to the connections? >> > > I did not implement WITH HOLD. Let me retest this, and look at old emails later when back at my laptop. Mason > >> Thanks, >> >> Mason >> >> >> >> >> 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. >> >> > > > > -- > Andrei Martsinchyk > > EntepriseDB Corporation > The Enterprise Postgres Company > > 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: Andrei.Martsinchyk <and...@en...> - 2010-12-03 16:31:30
|
Mason, 2010/12/3 Mason Sharp <mas...@en...>: > On 12/1/10 1:53 PM, Andrei.Martsinchyk wrote: >> >> Hi Benny, >> >> Thanks for pointing this out. I tested with a program using Postgres C >> library and extended query protocol. >> For you and anyone else who want to test I am attaching the test >> program and simple Makefile. >> I fixed the segmentation fault (updated patch is attached), but >> anyway, PREPARE / EXECUTE commands do not work properly. >> > > It looks like it is still not quite right: > > > mds1=# create table mytab (col1 int, col2 int); > CREATE TABLE > mds1=# prepare p (int, int) AS INSERT INTO mytab VALUES ($1, $2); > PREPARE > mds1=# execute p (1,2); > INSERT 0 1 > mds1=# select * from mytab; > col1 | col2 > ------+------ > (0 rows) > > It does not find the row that should have been inserted. > Yes, I mentioned the PREPARE command does not work properly. In this particular case it is inserting row into Coordinator database and not visible for select. > Also, one other question- the session seems to retain the fact that there > are associated prepared statements. Does that mean that the pooler will not > put these back in the pool until all are deallocated? > Coordinator does not prepare statements on datanodes, so connection can be released at the transaction end. > On a related note, for the WITH HOLD cursors you implemented, did you also > do something to hold on to the connections? > I did not implement WITH HOLD. > Thanks, > > Mason > > > > > 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. > > -- Andrei Martsinchyk EntepriseDB Corporation The Enterprise Postgres Company 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: Mason S. <mas...@en...> - 2010-12-03 14:26:27
|
On 12/1/10 1:53 PM, Andrei.Martsinchyk wrote: > Hi Benny, > > Thanks for pointing this out. I tested with a program using Postgres C > library and extended query protocol. > For you and anyone else who want to test I am attaching the test > program and simple Makefile. > I fixed the segmentation fault (updated patch is attached), but > anyway, PREPARE / EXECUTE commands do not work properly. > It looks like it is still not quite right: mds1=# create table mytab (col1 int, col2 int); CREATE TABLE mds1=# prepare p (int, int) AS INSERT INTO mytab VALUES ($1, $2); PREPARE mds1=# execute p (1,2); INSERT 0 1 mds1=# select * from mytab; col1 | col2 ------+------ (0 rows) It does not find the row that should have been inserted. Also, one other question- the session seems to retain the fact that there are associated prepared statements. Does that mean that the pooler will not put these back in the pool until all are deallocated? On a related note, for the WITH HOLD cursors you implemented, did you also do something to hold on to the connections? Thanks, Mason 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-12-03 06:18:10
|
It looks that make[4] was successful. I'm afraid there could be another error in some subdirectory under .../backend/ The following is a typical configure options we're using in our local test. ../configure CFLAGS='-O2 -DPGXC' --enable-debug --enable-depend --disable-rpath --prefix=/pg2/sudoutaka/pgsql_pg2 I hope it helps. Regards; --- Koichi (2010年12月03日 00:24), Devrim GÜNDÜZ wrote: > On Thu, 2010-12-02 at 19:00 +0900, Koichi Suzuki wrote: >> I think you should just remove libpthread from the spec file. Sorry >> I'm not familiar with building rpm. XC's configure does not include >> pthread staff by default. I hope it helps. > > Thanks, I disabled --enable-thread-safety flag. Now I'm getting strange > error. I can't see any problem below, or am I missing something? > > gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DPGXC -DPGXC -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -fwrapv -I../../../../src/include -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/include -c -o snapmgr.o snapmgr.c > ( echo src/backend/utils/sort/logtape.o src/backend/utils/sort/tuplesort.o src/backend/utils/sort/tuplestore.o )>objfiles.txt > make[5]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/backend/utils/sort' > ( echo src/backend/utils/time/combocid.o src/backend/utils/time/tqual.o src/backend/utils/time/snapmgr.o )>objfiles.txt > make[5]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/backend/utils/time' > ( cat adt/objfiles.txt cache/objfiles.txt error/objfiles.txt fmgr/objfiles.txt hash/objfiles.txt init/objfiles.txt mb/objfiles.txt misc/objfiles.txt mmgr/objfiles.txt resowner/objfiles.txt sort/objfiles.txt time/objfiles.txt; echo src/backend/utils/fmgrtab.o )>objfiles.txt > make[4]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/backend/utils' > make[3]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/backend' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc' > error: Bad exit status from /var/tmp/rpm-tmp.86900 (%build) > > Regards, > |
|
From: Devrim G. <de...@gu...> - 2010-12-02 15:25:59
|
On Thu, 2010-12-02 at 19:00 +0900, Koichi Suzuki wrote: > I think you should just remove libpthread from the spec file. Sorry > I'm not familiar with building rpm. XC's configure does not include > pthread staff by default. I hope it helps. Thanks, I disabled --enable-thread-safety flag. Now I'm getting strange error. I can't see any problem below, or am I missing something? gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DPGXC -DPGXC -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -fwrapv -I../../../../src/include -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/include -c -o snapmgr.o snapmgr.c ( echo src/backend/utils/sort/logtape.o src/backend/utils/sort/tuplesort.o src/backend/utils/sort/tuplestore.o ) >objfiles.txt make[5]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/backend/utils/sort' ( echo src/backend/utils/time/combocid.o src/backend/utils/time/tqual.o src/backend/utils/time/snapmgr.o ) >objfiles.txt make[5]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/backend/utils/time' ( cat adt/objfiles.txt cache/objfiles.txt error/objfiles.txt fmgr/objfiles.txt hash/objfiles.txt init/objfiles.txt mb/objfiles.txt misc/objfiles.txt mmgr/objfiles.txt resowner/objfiles.txt sort/objfiles.txt time/objfiles.txt; echo src/backend/utils/fmgrtab.o ) >objfiles.txt make[4]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/backend/utils' make[3]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/backend' make[2]: *** [all] Error 2 make[2]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc' error: Bad exit status from /var/tmp/rpm-tmp.86900 (%build) Regards, -- Devrim GÜNDÜZ PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer PostgreSQL RPM Repository: http://yum.pgrpms.org Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz |
|
From: Mason S. <mas...@en...> - 2010-12-02 13:17:35
|
On 12/1/10 11:40 PM, Michael Paquier wrote: > Sorry for my late reply. > > On Wed, Dec 1, 2010 at 7:34 AM, Mason Sharp > <mas...@en... <mailto:mas...@en...>> > wrote: > > >> >> For statement_timestamp() do we perform a separate operation >> through >> GTM, or do we do a delta similar to clock_timestamp()? >> >> statement_timestamo and transaction timestamp base their >> calculations based on delta calculated with GTM. >> clock_timestamp does not do anything with GTM, it just uses the >> local node timestamp. >> > Transaction_timestamp should just use the value piggybacked from > GTM with XID and not a delta though. The same value should be used > on all nodes involved in the transaction, right? > > > When a transaction is begun on a node, the transaction timestamp is > sent along with snapshot and gxid. > The value sent is of course the one calculated at Coordinator. > > You are right that we should send directly the timestamp value got at > GTM... > But if you have a look at the code, in xact.c > when a call of statement_timestamp is made, we calculate it based on > the local start timestamp and the delta value: > stmtStartTimestamp + GTMdeltaTimestamp > > Delta is itself calculated when received with this: > GTMdeltaTimestamp = GTMxactStartTimestamp - stmtStartTimestamp > > So we basically we give the timestamp value received from GTM. > > The important point is linked to stmtStartTimestamp. > This variable is constant inside a transaction, but it is changed when > running statements out of a transaction block. > > I think it is important to keep algorithm the way it is done now. > OK it complicates a little bit transaction timestamp calculation by > using the delta twice. > But the result is the same, and it permits to take into account both > transaction timestamp and statement timestamp cases when calling > statement_timestamp in xact.c. That seems a bit confusing. I think it would be cleaner to simply use the passed over from GTM timestamp for statement_timestamp. Is this same double calculation also being used for now()? Thanks, Mason > > -- > Michael Paquier > http://michaelpq.users.sourceforge.net > -- 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: Pavan D. <pav...@gm...> - 2010-12-02 10:17:48
|
On Tue, Nov 30, 2010 at 1:57 PM, Michael Paquier <mic...@gm...>wrote: > Hi all, > > Please see attached a patch that corrects 2PC (2 phase commit) in the case > of an implicit 2PC. > I think we should try to minimize changes to CommitTransaction. Why not use the PrepareTransaction() to prepare the transaction instead of duplicating that code inside CommitTransaction ? Also, it would be nice if you can take away new code in a separate function and call that, something like AtEOXact_PGXC() or something like that. Thanks, Pavan -- Pavan Deolasee EnterpriseDB http://www.enterprisedb.com |
|
From: Koichi S. <ko...@in...> - 2010-12-02 09:57:31
|
Devrim-san; (2010年12月02日 18:45), Devrim GÜNDÜZ wrote: > Hi, > > On Thu, 2010-12-02 at 12:59 +0900, Koichi Suzuki wrote: > >> It's because XC does not support pthread yet. Please remove pthread >> staff. > > Ok, *how* do I do that? Any configure options? I think you should just remove libpthread from the spec file. Sorry I'm not familiar with building rpm. XC's configure does not include pthread staff by default. I hope it helps. > >> Also, XC was tested only in 64bit environment. > > Ok. Any particular OS? Are you testing on Red Hat, too? > > Regards, Yes, we're testing with Cent-OS. RPM should be the same as RHEL5. --- Koichi |
|
From: Devrim G. <de...@gu...> - 2010-12-02 09:46:06
|
Hi, On Thu, 2010-12-02 at 12:59 +0900, Koichi Suzuki wrote: > It's because XC does not support pthread yet. Please remove pthread > staff. Ok, *how* do I do that? Any configure options? > Also, XC was tested only in 64bit environment. Ok. Any particular OS? Are you testing on Red Hat, too? Regards, -- Devrim GÜNDÜZ PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer PostgreSQL RPM Repository: http://yum.pgrpms.org Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz |
|
From: Michael P. <mic...@gm...> - 2010-12-02 04:40:29
|
Sorry for my late reply. On Wed, Dec 1, 2010 at 7:34 AM, Mason Sharp <mas...@en...>wrote: > > >> For statement_timestamp() do we perform a separate operation through >> GTM, or do we do a delta similar to clock_timestamp()? >> > statement_timestamo and transaction timestamp base their calculations based > on delta calculated with GTM. > clock_timestamp does not do anything with GTM, it just uses the local node > timestamp. > > Transaction_timestamp should just use the value piggybacked from GTM with > XID and not a delta though. The same value should be used on all nodes > involved in the transaction, right? > When a transaction is begun on a node, the transaction timestamp is sent along with snapshot and gxid. The value sent is of course the one calculated at Coordinator. You are right that we should send directly the timestamp value got at GTM... But if you have a look at the code, in xact.c when a call of statement_timestamp is made, we calculate it based on the local start timestamp and the delta value: stmtStartTimestamp + GTMdeltaTimestamp Delta is itself calculated when received with this: GTMdeltaTimestamp = GTMxactStartTimestamp - stmtStartTimestamp So we basically we give the timestamp value received from GTM. The important point is linked to stmtStartTimestamp. This variable is constant inside a transaction, but it is changed when running statements out of a transaction block. I think it is important to keep algorithm the way it is done now. OK it complicates a little bit transaction timestamp calculation by using the delta twice. But the result is the same, and it permits to take into account both transaction timestamp and statement timestamp cases when calling statement_timestamp in xact.c. -- Michael Paquier http://michaelpq.users.sourceforge.net |
|
From: Koichi S. <ko...@in...> - 2010-12-02 03:56:14
|
It's because XC does not support pthread yet. Please remove pthread staff. Also, XC was tested only in 64bit environment. I hope these will help. Best Regards; --- Koichi Suzuki (2010年12月02日 01:18), Devrim GÜNDÜZ wrote: > > Hi, > > I'm getting build errors while trying to build Postgres-XC on Fedora 13 > and RHEL 5. > > Spec files are here, which are pretty much the same: > > http://svn.pgrpms.org/browser/rpm/redhat/8.4/postgres-xc/EL-5/postgres-xc-8.4.spec > http://svn.pgrpms.org/browser/rpm/redhat/8.4/postgres-xc/F-13/postgres-xc-8.4.spec > > Here are the errors: > > F-13 (gcc 4.4.4) (on both 32 and 64 bit systems) > > cat: ../../src/interfaces/libpq/objfiles.txt: No such file or directory > gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DPGXC -DPGXC -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -fwrapv -L../../src/port -L/usr/lib64 -Wl,--as-needed -L../../src/gtm/libpg -Wl,-E access/common/heaptuple.o access/common/indextuple.o access/common/printtup.o access/common/reloptions.o access/common/scankey.o access/common/tupdesc.o access/gist/gist.o access/gist/gistutil.o access/gist/gistxlog.o access/gist/gistvacuum.o access/gist/gistget.o access/gist/gistscan.o access/gist/gistproc.o access/gist/gistsplit.o access/hash/hash.o access/hash/hashfunc.o access/hash/hashinsert.o access/hash/hashovfl.o access/hash/hashpage.o access/hash/hashscan.o access/hash/hashsearch.o access/hash/hashsort.o access/hash/hashutil.o access/heap/heapam.o access/heap/hio.o access/heap/pruneheap.o access/heap/rewriteheap.o access/heap/syncscan.o acce ss/heap/tuptoaster.o access/heap/visibilitymap.o access/index/genam.o access/index/indexam.o access/nbtree/nbtcompare.o access/nbtree/nbtinsert.o access/nbtree/nbtpage.o access/nbtree/nbtree.o access/nbtree/nbtsearch.o access/nbtree/nbtutils.o access/nbtree/nbtsort.o access/nbtree/nbtxlog.o access/transam/clog.o access/transam/transam.o access/transam/varsup.o access/transam/xact.o access/transam/xlog.o access/transam/xlogutils.o access/transam/rmgr.o access/transam/slru.o access/transam/subtrans.o access/transam/multixact.o access/transam/twophase.o access/transam/twophase_rmgr.o access/transam/gtm.o access/gin/ginutil.o access/gin/gininsert.o access/gin/ginxlog.o access/gin/ginentrypage.o access/gin/gindatapage.o access/gin/ginbtree.o access/gin/ginscan.o access/gin/ginget.o access/gin/ginvacuum.o access/gin/ginarrayproc.o access/gin/ginbulk.o access/gin/ginfast.o bootstrap/bootparse.o bootstrap/bootstrap.o catalog/catalog.o catalog/dependency.o catalog/heap.o catalog/index ..o catalog/indexing.o catalog/namespace.o catalog/aclchk.o catalog/pg_aggregate.o catalog/pg_constraint.o catalog/pg_conversion.o catalog/pg_depend.o catalog/pg_enum.o catalog/pg_inherits.o catalog/pg_largeobject.o catalog/pg_namespace.o catalog/pg_operator.o catalog/pg_proc.o catalog/pg_shdepend.o catalog/pg_type.o catalog/pgxc_class.o catalog/storage.o catalog/toasting.o parser/analyze.o parser/gram.o parser/keywords.o parser/parser.o parser/parse_agg.o parser/parse_cte.o parser/parse_clause.o parser/parse_expr.o parser/parse_func.o parser/parse_node.o parser/parse_oper.o parser/parse_relation.o parser/parse_type.o parser/parse_coerce.o parser/parse_target.o parser/parse_utilcmd.o parser/scansup.o parser/kwlookup.o commands/aggregatecmds.o commands/alter.o commands/analyze.o commands/async.o commands/cluster.o commands/comment.o commands/conversioncmds.o commands/copy.o commands/dbcommands.o commands/define.o commands/discard.o commands/explain.o commands/foreigncmds.o comm ands/functioncmds.o commands/indexcmds.o commands/lockcmds.o commands/operatorcmds.o commands/opclasscmds.o commands/portalcmds.o commands/prepare.o commands/proclang.o commands/schemacmds.o commands/sequence.o commands/tablecmds.o commands/tablespace.o commands/trigger.o commands/tsearchcmds.o commands/typecmds.o commands/user.o commands/vacuum.o commands/vacuumlazy.o commands/variable.o commands/view.o executor/execAmi.o executor/execCurrent.o executor/execGrouping.o executor/execJunk.o executor/execMain.o executor/execProcnode.o executor/execQual.o executor/execScan.o executor/execTuples.o executor/execUtils.o executor/functions.o executor/instrument.o executor/nodeAppend.o executor/nodeAgg.o executor/nodeBitmapAnd.o executor/nodeBitmapOr.o executor/nodeBitmapHeapscan.o executor/nodeBitmapIndexscan.o executor/nodeHash.o executor/nodeHashjoin.o executor/nodeIndexscan.o executor/nodeMaterial.o executor/nodeMergejoin.o executor/nodeNestloop.o executor/nodeFunctionscan.o execu tor/nodeRecursiveunion.o executor/nodeResult.o executor/nodeSeqscan.o executor/nodeSetOp.o executor/nodeSort.o executor/nodeUnique.o executor/nodeValuesscan.o executor/nodeCtescan.o executor/nodeWorktablescan.o executor/nodeLimit.o executor/nodeGroup.o executor/nodeSubplan.o executor/nodeSubqueryscan.o executor/nodeTidscan.o executor/nodeWindowAgg.o executor/tstoreReceiver.o executor/spi.o foreign/foreign.o lib/dllist.o lib/stringinfo.o libpq/be-fsstubs.o libpq/be-secure.o libpq/auth.o libpq/crypt.o libpq/hba.o libpq/ip.o libpq/md5.o libpq/pqcomm.o libpq/pqformat.o libpq/pqsignal.o pgxc/locator/locator.o pgxc/plan/planner.o pgxc/pool/pgxcnode.o pgxc/pool/execRemote.o pgxc/pool/poolmgr.o pgxc/pool/poolcomm.o pgxc/pool/postgresql_fdw.o main/main.o nodes/nodeFuncs.o nodes/nodes.o nodes/list.o nodes/bitmapset.o nodes/tidbitmap.o nodes/copyfuncs.o nodes/equalfuncs.o nodes/makefuncs.o nodes/outfuncs.o nodes/readfuncs.o nodes/print.o nodes/read.o nodes/params.o nodes/value.o optimiz er/geqo/geqo_copy.o optimizer/geqo/geqo_eval.o optimizer/geqo/geqo_main.o optimizer/geqo/geqo_misc.o optimizer/geqo/geqo_mutation.o optimizer/geqo/geqo_pool.o optimizer/geqo/geqo_recombination.o optimizer/geqo/geqo_selection.o optimizer/geqo/geqo_erx.o optimizer/geqo/geqo_pmx.o optimizer/geqo/geqo_cx.o optimizer/geqo/geqo_px.o optimizer/geqo/geqo_ox1.o optimizer/geqo/geqo_ox2.o optimizer/path/allpaths.o optimizer/path/clausesel.o optimizer/path/costsize.o optimizer/path/equivclass.o optimizer/path/indxpath.o optimizer/path/joinpath.o optimizer/path/joinrels.o optimizer/path/orindxpath.o optimizer/path/pathkeys.o optimizer/path/tidpath.o optimizer/plan/createplan.o optimizer/plan/initsplan.o optimizer/plan/planagg.o optimizer/plan/planmain.o optimizer/plan/planner.o optimizer/plan/setrefs.o optimizer/plan/subselect.o optimizer/prep/prepjointree.o optimizer/prep/prepqual.o optimizer/prep/preptlist.o optimizer/prep/prepunion.o optimizer/util/clauses.o optimizer/util/joininfo.o o ptimizer/util/pathnode.o optimizer/util/placeholder.o optimizer/util/plancat.o optimizer/util/predtest.o optimizer/util/relnode.o optimizer/util/restrictinfo.o optimizer/util/tlist.o optimizer/util/var.o port/dynloader.o port/pg_sema.o port/pg_shmem.o postmaster/autovacuum.o postmaster/bgwriter.o postmaster/fork_process.o postmaster/pgarch.o postmaster/pgstat.o postmaster/postmaster.o postmaster/syslogger.o postmaster/walwriter.o regex/regcomp.o regex/regerror.o regex/regexec.o regex/regfree.o rewrite/rewriteRemove.o rewrite/rewriteDefine.o rewrite/rewriteHandler.o rewrite/rewriteManip.o rewrite/rewriteSupport.o storage/buffer/buf_table.o storage/buffer/buf_init.o storage/buffer/bufmgr.o storage/buffer/freelist.o storage/buffer/localbuf.o storage/file/fd.o storage/file/buffile.o storage/freespace/freespace.o storage/freespace/fsmpage.o storage/freespace/indexfsm.o storage/ipc/ipc.o storage/ipc/ipci.o storage/ipc/pmsignal.o storage/ipc/procarray.o storage/ipc/shmem.o storage/i pc/shmqueue.o storage/ipc/sinval.o storage/ipc/sinvaladt.o storage/large_object/inv_api.o storage/lmgr/lmgr.o storage/lmgr/lock.o storage/lmgr/proc.o storage/lmgr/deadlock.o storage/lmgr/lwlock.o storage/lmgr/spin.o storage/lmgr/s_lock.o storage/page/bufpage.o storage/page/itemptr.o storage/smgr/md.o storage/smgr/smgr.o storage/smgr/smgrtype.o tcop/dest.o tcop/fastpath.o tcop/postgres.o tcop/pquery.o tcop/utility.o tsearch/ts_locale.o tsearch/ts_parse.o tsearch/wparser.o tsearch/wparser_def.o tsearch/dict.o tsearch/dict_simple.o tsearch/dict_synonym.o tsearch/dict_thesaurus.o tsearch/dict_ispell.o tsearch/regis.o tsearch/spell.o tsearch/to_tsany.o tsearch/ts_selfuncs.o tsearch/ts_typanalyze.o tsearch/ts_utils.o utils/adt/acl.o utils/adt/arrayfuncs.o utils/adt/array_userfuncs.o utils/adt/arrayutils.o utils/adt/bool.o utils/adt/cash.o utils/adt/char.o utils/adt/date.o utils/adt/datetime.o utils/adt/datum.o utils/adt/domains.o utils/adt/enum.o utils/adt/float.o utils/adt/format_ type.o utils/adt/geo_ops.o utils/adt/geo_selfuncs.o utils/adt/int.o utils/adt/int8.o utils/adt/like.o utils/adt/lockfuncs.o utils/adt/misc.o utils/adt/nabstime.o utils/adt/name.o utils/adt/numeric.o utils/adt/numutils.o utils/adt/oid.o utils/adt/oracle_compat.o utils/adt/pseudotypes.o utils/adt/rowtypes.o utils/adt/regexp.o utils/adt/regproc.o utils/adt/ruleutils.o utils/adt/selfuncs.o utils/adt/tid.o utils/adt/timestamp.o utils/adt/varbit.o utils/adt/varchar.o utils/adt/varlena.o utils/adt/version.o utils/adt/xid.o utils/adt/network.o utils/adt/mac.o utils/adt/inet_net_ntop.o utils/adt/inet_net_pton.o utils/adt/ri_triggers.o utils/adt/pg_lzcompress.o utils/adt/pg_locale.o utils/adt/formatting.o utils/adt/ascii.o utils/adt/quote.o utils/adt/pgstatfuncs.o utils/adt/encode.o utils/adt/dbsize.o utils/adt/genfile.o utils/adt/trigfuncs.o utils/adt/tsginidx.o utils/adt/tsgistidx.o utils/adt/tsquery.o utils/adt/tsquery_cleanup.o utils/adt/tsquery_gist.o utils/adt/tsquery_op.o utils/ adt/tsquery_rewrite.o utils/adt/tsquery_util.o utils/adt/tsrank.o utils/adt/tsvector.o utils/adt/tsvector_op.o utils/adt/tsvector_parser.o utils/adt/txid.o utils/adt/uuid.o utils/adt/windowfuncs.o utils/adt/xml.o utils/cache/catcache.o utils/cache/inval.o utils/cache/plancache.o utils/cache/relcache.o utils/cache/syscache.o utils/cache/lsyscache.o utils/cache/typcache.o utils/cache/ts_cache.o utils/error/assert.o utils/error/elog.o utils/fmgr/dfmgr.o utils/fmgr/fmgr.o utils/fmgr/funcapi.o utils/hash/dynahash.o utils/hash/hashfn.o utils/hash/pg_crc.o utils/init/flatfiles.o utils/init/globals.o utils/init/miscinit.o utils/init/postinit.o utils/mb/encnames.o utils/mb/conv.o utils/mb/mbutils.o utils/mb/wchar.o utils/mb/wstrcmp.o utils/mb/wstrncmp.o utils/misc/guc.o utils/misc/help_config.o utils/misc/pg_rusage.o utils/misc/ps_status.o utils/misc/superuser.o utils/misc/tzparser.o utils/mmgr/aset.o utils/mmgr/mcxt.o utils/mmgr/portalmem.o utils/resowner/resowner.o utils/sort/logtap e.o utils/sort/tuplesort.o utils/sort/tuplestore.o utils/time/combocid.o utils/time/tqual.o utils/time/snapmgr.o utils/fmgrtab.o ../../src/timezone/localtime.o ../../src/timezone/strftime.o ../../src/timezone/pgtz.o utils/probes.o ../../src/interfaces/libpq/fe-connect.o ../../src/interfaces/libpq/fe-secure.o ../../src/interfaces/libpq/fe-misc.o ../../src/interfaces/libpq/fe-protocol3.o ../../src/interfaces/libpq/fe-protocol2.o ../../src/interfaces/libpq/fe-exec.o ../../src/interfaces/libpq/fe-auth.o ../../src/interfaces/libpq/pqexpbuffer.o ../../src/port/libpgport_srv.a ../../src/gtm/client/libgtmclient.a ../../src/gtm/common/libgtm.a ../../src/gtm/libpq/libpqcomm.a -lxslt -lxml2 -lpam -lssl -lcrypto -lkrb5 -lcom_err -lgssapi_krb5 -lcrypt -ldl -lm -lldap -o postgres > /usr/bin/ld: ../../src/interfaces/libpq/fe-secure.o: undefined reference to symbol 'pthread_sigmask@@GLIBC_2.2.5' > /usr/bin/ld: note: 'pthread_sigmask@@GLIBC_2.2.5' is defined in DSO /lib64/libpthread.so.0 so try adding it to the linker command line > /lib64/libpthread.so.0: could not read symbols: Invalid operation > collect2: ld returned 1 exit status > make[3]: *** [postgres] Error 1 > > RHEL 5 (GCC 4.1.2, 32 bit) > > make[4]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/interfaces/libpq' > cat: ../../src/interfaces/libpq/objfiles.txt: No such file or directory > gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -DPGXC -DPGXC -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -fwrapv -L../../src/port -L/usr/lib -L/usr/lib -L../../src/gtm/libpg -Wl,-E access/common/heaptuple.o access/common/indextuple.o access/common/printtup.o access/common/reloptions.o access/common/scankey.o access/common/tupdesc.o access/gist/gist.o access/gist/gistutil.o access/gist/gistxlog.o access/gist/gistvacuum.o access/gist/gistget.o access/gist/gistscan.o access/gist/gistproc.o access/gist/gistsplit.o access/hash/hash.o access/hash/hashfunc.o access/hash/hashinsert.o access/hash/hashovfl.o access/hash/hashpage.o access/hash/hashscan.o access/hash/hashsearch.o access/hash/hashsort.o access/hash/hashutil.o access/heap/heapam.o access/heap/hio.o access/heap/pruneheap.o access/heap/rewrit eheap.o access/heap/syncscan.o access/heap/tuptoaster.o access/heap/visibilitymap.o access/index/genam.o access/index/indexam.o access/nbtree/nbtcompare.o access/nbtree/nbtinsert.o access/nbtree/nbtpage.o access/nbtree/nbtree.o access/nbtree/nbtsearch.o access/nbtree/nbtutils.o access/nbtree/nbtsort.o access/nbtree/nbtxlog.o access/transam/clog.o access/transam/transam.o access/transam/varsup.o access/transam/xact.o access/transam/xlog.o access/transam/xlogutils.o access/transam/rmgr.o access/transam/slru.o access/transam/subtrans.o access/transam/multixact.o access/transam/twophase.o access/transam/twophase_rmgr.o access/transam/gtm.o access/gin/ginutil.o access/gin/gininsert.o access/gin/ginxlog.o access/gin/ginentrypage.o access/gin/gindatapage.o access/gin/ginbtree.o access/gin/ginscan.o access/gin/ginget.o access/gin/ginvacuum.o access/gin/ginarrayproc.o access/gin/ginbulk.o access/gin/ginfast.o bootstrap/bootparse.o bootstrap/bootstrap.o catalog/catalog.o catalog/depend ency.o catalog/heap.o catalog/index.o catalog/indexing.o catalog/namespace.o catalog/aclchk.o catalog/pg_aggregate.o catalog/pg_constraint.o catalog/pg_conversion.o catalog/pg_depend.o catalog/pg_enum.o catalog/pg_inherits.o catalog/pg_largeobject.o catalog/pg_namespace.o catalog/pg_operator.o catalog/pg_proc.o catalog/pg_shdepend.o catalog/pg_type.o catalog/pgxc_class.o catalog/storage.o catalog/toasting.o parser/analyze.o parser/gram.o parser/keywords.o parser/parser.o parser/parse_agg.o parser/parse_cte.o parser/parse_clause.o parser/parse_expr.o parser/parse_func.o parser/parse_node.o parser/parse_oper.o parser/parse_relation.o parser/parse_type.o parser/parse_coerce.o parser/parse_target.o parser/parse_utilcmd.o parser/scansup.o parser/kwlookup.o commands/aggregatecmds.o commands/alter.o commands/analyze.o commands/async.o commands/cluster.o commands/comment.o commands/conversioncmds.o commands/copy.o commands/dbcommands.o commands/define.o commands/discard.o commands/ex plain.o commands/foreigncmds.o commands/functioncmds.o commands/indexcmds.o commands/lockcmds.o commands/operatorcmds.o commands/opclasscmds.o commands/portalcmds.o commands/prepare.o commands/proclang.o commands/schemacmds.o commands/sequence.o commands/tablecmds.o commands/tablespace.o commands/trigger.o commands/tsearchcmds.o commands/typecmds.o commands/user.o commands/vacuum.o commands/vacuumlazy.o commands/variable.o commands/view.o executor/execAmi.o executor/execCurrent.o executor/execGrouping.o executor/execJunk.o executor/execMain.o executor/execProcnode.o executor/execQual.o executor/execScan.o executor/execTuples.o executor/execUtils.o executor/functions.o executor/instrument.o executor/nodeAppend.o executor/nodeAgg.o executor/nodeBitmapAnd.o executor/nodeBitmapOr.o executor/nodeBitmapHeapscan.o executor/nodeBitmapIndexscan.o executor/nodeHash.o executor/nodeHashjoin.o executor/nodeIndexscan.o executor/nodeMaterial.o executor/nodeMergejoin.o executor/nodeNestloop. o executor/nodeFunctionscan.o executor/nodeRecursiveunion.o executor/nodeResult.o executor/nodeSeqscan.o executor/nodeSetOp.o executor/nodeSort.o executor/nodeUnique.o executor/nodeValuesscan.o executor/nodeCtescan.o executor/nodeWorktablescan.o executor/nodeLimit.o executor/nodeGroup.o executor/nodeSubplan.o executor/nodeSubqueryscan.o executor/nodeTidscan.o executor/nodeWindowAgg.o executor/tstoreReceiver.o executor/spi.o foreign/foreign.o lib/dllist.o lib/stringinfo.o libpq/be-fsstubs.o libpq/be-secure.o libpq/auth.o libpq/crypt.o libpq/hba.o libpq/ip.o libpq/md5.o libpq/pqcomm.o libpq/pqformat.o libpq/pqsignal.o pgxc/locator/locator.o pgxc/plan/planner.o pgxc/pool/pgxcnode.o pgxc/pool/execRemote.o pgxc/pool/poolmgr.o pgxc/pool/poolcomm.o pgxc/pool/postgresql_fdw.o main/main.o nodes/nodeFuncs.o nodes/nodes.o nodes/list.o nodes/bitmapset.o nodes/tidbitmap.o nodes/copyfuncs.o nodes/equalfuncs.o nodes/makefuncs.o nodes/outfuncs.o nodes/readfuncs.o nodes/print.o nodes/read.o n odes/params.o nodes/value.o optimizer/geqo/geqo_copy.o optimizer/geqo/geqo_eval.o optimizer/geqo/geqo_main.o optimizer/geqo/geqo_misc.o optimizer/geqo/geqo_mutation.o optimizer/geqo/geqo_pool.o optimizer/geqo/geqo_recombination.o optimizer/geqo/geqo_selection.o optimizer/geqo/geqo_erx.o optimizer/geqo/geqo_pmx.o optimizer/geqo/geqo_cx.o optimizer/geqo/geqo_px.o optimizer/geqo/geqo_ox1.o optimizer/geqo/geqo_ox2.o optimizer/path/allpaths.o optimizer/path/clausesel.o optimizer/path/costsize.o optimizer/path/equivclass.o optimizer/path/indxpath.o optimizer/path/joinpath.o optimizer/path/joinrels.o optimizer/path/orindxpath.o optimizer/path/pathkeys.o optimizer/path/tidpath.o optimizer/plan/createplan.o optimizer/plan/initsplan.o optimizer/plan/planagg.o optimizer/plan/planmain.o optimizer/plan/planner.o optimizer/plan/setrefs.o optimizer/plan/subselect.o optimizer/prep/prepjointree.o optimizer/prep/prepqual.o optimizer/prep/preptlist.o optimizer/prep/prepunion.o optimizer/util/cl auses.o optimizer/util/joininfo.o optimizer/util/pathnode.o optimizer/util/placeholder.o optimizer/util/plancat.o optimizer/util/predtest.o optimizer/util/relnode.o optimizer/util/restrictinfo.o optimizer/util/tlist.o optimizer/util/var.o port/dynloader.o port/pg_sema.o port/pg_shmem.o postmaster/autovacuum.o postmaster/bgwriter.o postmaster/fork_process.o postmaster/pgarch.o postmaster/pgstat.o postmaster/postmaster.o postmaster/syslogger.o postmaster/walwriter.o regex/regcomp.o regex/regerror.o regex/regexec.o regex/regfree.o rewrite/rewriteRemove.o rewrite/rewriteDefine.o rewrite/rewriteHandler.o rewrite/rewriteManip.o rewrite/rewriteSupport.o storage/buffer/buf_table.o storage/buffer/buf_init.o storage/buffer/bufmgr.o storage/buffer/freelist.o storage/buffer/localbuf.o storage/file/fd.o storage/file/buffile.o storage/freespace/freespace.o storage/freespace/fsmpage.o storage/freespace/indexfsm.o storage/ipc/ipc.o storage/ipc/ipci.o storage/ipc/pmsignal.o storage/ipc/procar ray.o storage/ipc/shmem.o storage/ipc/shmqueue.o storage/ipc/sinval.o storage/ipc/sinvaladt.o storage/large_object/inv_api.o storage/lmgr/lmgr.o storage/lmgr/lock.o storage/lmgr/proc.o storage/lmgr/deadlock.o storage/lmgr/lwlock.o storage/lmgr/spin.o storage/lmgr/s_lock.o storage/page/bufpage.o storage/page/itemptr.o storage/smgr/md.o storage/smgr/smgr.o storage/smgr/smgrtype.o tcop/dest.o tcop/fastpath.o tcop/postgres.o tcop/pquery.o tcop/utility.o tsearch/ts_locale.o tsearch/ts_parse.o tsearch/wparser.o tsearch/wparser_def.o tsearch/dict.o tsearch/dict_simple.o tsearch/dict_synonym.o tsearch/dict_thesaurus.o tsearch/dict_ispell.o tsearch/regis.o tsearch/spell.o tsearch/to_tsany.o tsearch/ts_selfuncs.o tsearch/ts_typanalyze.o tsearch/ts_utils.o utils/adt/acl.o utils/adt/arrayfuncs.o utils/adt/array_userfuncs.o utils/adt/arrayutils.o utils/adt/bool.o utils/adt/cash.o utils/adt/char.o utils/adt/date.o utils/adt/datetime.o utils/adt/datum.o utils/adt/domains.o utils/adt/enum.o utils/adt/float.o utils/adt/format_type.o utils/adt/geo_ops.o utils/adt/geo_selfuncs.o utils/adt/int.o utils/adt/int8.o utils/adt/like.o utils/adt/lockfuncs.o utils/adt/misc.o utils/adt/nabstime.o utils/adt/name.o utils/adt/numeric.o utils/adt/numutils.o utils/adt/oid.o utils/adt/oracle_compat.o utils/adt/pseudotypes.o utils/adt/rowtypes.o utils/adt/regexp.o utils/adt/regproc.o utils/adt/ruleutils.o utils/adt/selfuncs.o utils/adt/tid.o utils/adt/timestamp.o utils/adt/varbit.o utils/adt/varchar.o utils/adt/varlena.o utils/adt/version.o utils/adt/xid.o utils/adt/network.o utils/adt/mac.o utils/adt/inet_net_ntop.o utils/adt/inet_net_pton.o utils/adt/ri_triggers.o utils/adt/pg_lzcompress.o utils/adt/pg_locale.o utils/adt/formatting.o utils/adt/ascii.o utils/adt/quote.o utils/adt/pgstatfuncs.o utils/adt/encode.o utils/adt/dbsize.o utils/adt/genfile.o utils/adt/trigfuncs.o utils/adt/tsginidx.o utils/adt/tsgistidx.o utils/adt/tsquery.o utils/adt/tsquery_cleanup.o utils/adt/tsquery_g ist.o utils/adt/tsquery_op.o utils/adt/tsquery_rewrite.o utils/adt/tsquery_util.o utils/adt/tsrank.o utils/adt/tsvector.o utils/adt/tsvector_op.o utils/adt/tsvector_parser.o utils/adt/txid.o utils/adt/uuid.o utils/adt/windowfuncs.o utils/adt/xml.o utils/cache/catcache.o utils/cache/inval.o utils/cache/plancache.o utils/cache/relcache.o utils/cache/syscache.o utils/cache/lsyscache.o utils/cache/typcache.o utils/cache/ts_cache.o utils/error/assert.o utils/error/elog.o utils/fmgr/dfmgr.o utils/fmgr/fmgr.o utils/fmgr/funcapi.o utils/hash/dynahash.o utils/hash/hashfn.o utils/hash/pg_crc.o utils/init/flatfiles.o utils/init/globals.o utils/init/miscinit.o utils/init/postinit.o utils/mb/encnames.o utils/mb/conv.o utils/mb/mbutils.o utils/mb/wchar.o utils/mb/wstrcmp.o utils/mb/wstrncmp.o utils/misc/guc.o utils/misc/help_config.o utils/misc/pg_rusage.o utils/misc/ps_status.o utils/misc/superuser.o utils/misc/tzparser.o utils/mmgr/aset.o utils/mmgr/mcxt.o utils/mmgr/portalmem.o utils/re sowner/resowner.o utils/sort/logtape.o utils/sort/tuplesort.o utils/sort/tuplestore.o utils/time/combocid.o utils/time/tqual.o utils/time/snapmgr.o utils/fmgrtab.o ../../src/timezone/localtime.o ../../src/timezone/strftime.o ../../src/timezone/pgtz.o ../../src/interfaces/libpq/fe-connect.o ../../src/interfaces/libpq/fe-secure.o ../../src/interfaces/libpq/fe-misc.o ../../src/interfaces/libpq/fe-protocol3.o ../../src/interfaces/libpq/fe-protocol2.o ../../src/interfaces/libpq/fe-exec.o ../../src/interfaces/libpq/fe-auth.o ../../src/interfaces/libpq/pqexpbuffer.o ../../src/port/libpgport_srv.a ../../src/gtm/client/libgtmclient.a ../../src/gtm/common/libgtm.a ../../src/gtm/libpq/libpqcomm.a -lxslt -lxml2 -lpam -lssl -lcrypto -lgssapi_krb5 -lcrypt -ldl -lm -lldap -o postgres > ../../src/interfaces/libpq/fe-secure.o: In function `pq_reset_sigpipe': > /var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/interfaces/libpq/fe-secure.c:1413: undefined reference to `pthread_sigmask' > ../../src/interfaces/libpq/fe-secure.o: In function `pq_block_sigpipe': > /var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/interfaces/libpq/fe-secure.c:1350: undefined reference to `pthread_sigmask' > collect2: ld returned 1 exit status > make[3]: *** [postgres] Error 1 > make[3]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/backend' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc' > error: Bad exit status from /var/tmp/rpm-tmp.79960 (%build) > > Regards, > > > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App& Earn a Chance To Win $500! > Tap into the largest installed PC base& get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > > > > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: Mason S. <mas...@en...> - 2010-12-01 19:19:29
|
On 12/1/10 5:51 AM, sch19831106 wrote: > Hi developers. > Excuse me! I am shen changhai. > ***************************** postgres-xc Environment > ******************************** > Executed statement " create aggregate " on the postgres-xc,statement > and results are as follows: > Statement: > create aggregate newavg2 (sfunc = int4pl, basetype = int4,stype = int4,finalfunc = int2um, initcond = '0'); > Results: > ERROR: aggregate ctype must be specified In Postgres-XC, you also need to specify a ctype function, as in XC aggregates are divided into 3 phases, not 2. I thought this was in the documentation. Here is some additional info from an email I received from Andrei Martsinchyk: Good description of CREATE AGGREGATE can be found in the Postgres docs: http://www.postgresql.org/docs/8.4/static/sql-createaggregate.html <http://www.postgresql.org/docs/8.4/static/sql-createaggregate.html> Postgres-XC added additional step (collection function) between transition and final calculation functions, and schema sfunc( internal-state, next-data-values ) ---> next-internal-state ffunc( internal-state ) ---> aggregate-value was changed to sfunc( node-internal-state, next-data-values ) ---> node-internal-state cfunc( coord-internal-state, node-internal-state ) ---> coord-internal-state ffunc( coord-internal-state ) ---> aggregate-value To reflect this change following parameters was added to CREATE AGGREGATE: CFUNC - collection function, CTYPE - collection data type, INITCOLLECT - (optional) initial collection value. It is hard to develop aggregate function from the scratch. For my testing I recreated existing functions under different name. Example: create aggregate mymin (int4) (sfunc=int4smaller, stype=int4, cfunc=int4smaller, ctype=int4); You can see the list of defined aggregate functions querying pg_aggregate table: select * pg_aggregate; You can also try and construct own aggregate function. You would need to choose functions for sfunc, cfunc and ffunc (component functions) from already defined in Postgres. You can see the list of defined functions querying pg_proc table: select * pg_proc; There are requirements for return types and parameter types of the component functions. cfunc: data type of the first parameter must be the same as return type. Data types of remaining parameters must be the same as data types of the aggregate function sfunc: must have two parameters, data type of first parameter must be the same as return type of sfunc, data type of second parameter must be the same as return type of cfunc ffunc: must have one parameter, data type must be the same as return type of sfunc. And finally data types, you can see the list of defined data types querying pg_type table: select * pg_type; Feel free to ask if you have a question. Regards, Mason > ******************************* pg Environment > *********************************** > Executed statement " create aggregate " on the pg,statement and > results are as follows: > Statement: > create aggregate newavg2 (sfunc = int4pl, basetype = int4,stype = int4,finalfunc = int2um, initcond = '0'); > Results: > ERROR: function int2um(integer) does not exist > The above results are correct? > Thanks! > ********************** > shen changhai > Email: sch...@16... <mailto:sch...@16...> > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App& Earn a Chance To Win $500! > Tap into the largest installed PC base& get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-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: Andrei.Martsinchyk <and...@en...> - 2010-12-01 18:53:25
|
Hi Benny, Thanks for pointing this out. I tested with a program using Postgres C library and extended query protocol. For you and anyone else who want to test I am attaching the test program and simple Makefile. I fixed the segmentation fault (updated patch is attached), but anyway, PREPARE / EXECUTE commands do not work properly. The problem with it of the same kind as reported by you (sending begin;command;). We are using original SQL statement to build up statement for datanodes. In some cases pure command text is not available - it contains garbage, like neighbour statement or ouiter command (PREPARE ... AS). Postgres parser does not split command, it just produces multiple Query trees, or inner Query. We want the command being sent to datanodes is built up based on the Query produced by parser, taking into account planner info. We are working on this. 2010/12/1 xiong wang <wan...@gm...>: > Dears, > > template1=# prepare a(int) as insert into t values($1); > LOG: statement: prepare a(int) as insert into t values($1); > > 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 26936) was terminated by signal 11: Segmentation fault > LOG: terminating any other active server processes > 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. > 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. > > Regards, > Benny > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > -- Andrei Martsinchyk EntepriseDB Corporation The Enterprise Postgres Company 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: Devrim G. <de...@gu...> - 2010-12-01 16:37:51
|
Hi, I'm getting build errors while trying to build Postgres-XC on Fedora 13 and RHEL 5. Spec files are here, which are pretty much the same: http://svn.pgrpms.org/browser/rpm/redhat/8.4/postgres-xc/EL-5/postgres-xc-8.4.spec http://svn.pgrpms.org/browser/rpm/redhat/8.4/postgres-xc/F-13/postgres-xc-8.4.spec Here are the errors: F-13 (gcc 4.4.4) (on both 32 and 64 bit systems) cat: ../../src/interfaces/libpq/objfiles.txt: No such file or directory gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DPGXC -DPGXC -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -fwrapv -L../../src/port -L/usr/lib64 -Wl,--as-needed -L../../src/gtm/libpg -Wl,-E access/common/heaptuple.o access/common/indextuple.o access/common/printtup.o access/common/reloptions.o access/common/scankey.o access/common/tupdesc.o access/gist/gist.o access/gist/gistutil.o access/gist/gistxlog.o access/gist/gistvacuum.o access/gist/gistget.o access/gist/gistscan.o access/gist/gistproc.o access/gist/gistsplit.o access/hash/hash.o access/hash/hashfunc.o access/hash/hashinsert.o access/hash/hashovfl.o access/hash/hashpage.o access/hash/hashscan.o access/hash/hashsearch.o access/hash/hashsort.o access/hash/hashutil.o access/heap/heapam.o access/heap/hio.o access/heap/pruneheap.o access/heap/rewriteheap.o access/heap/syncscan.o access/heap/tuptoaster.o access/heap/visibilitymap.o access/index/genam.o access/index/indexam.o access/nbtree/nbtcompare.o access/nbtree/nbtinsert.o access/nbtree/nbtpage.o access/nbtree/nbtree.o access/nbtree/nbtsearch.o access/nbtree/nbtutils.o access/nbtree/nbtsort.o access/nbtree/nbtxlog.o access/transam/clog.o access/transam/transam.o access/transam/varsup.o access/transam/xact.o access/transam/xlog.o access/transam/xlogutils.o access/transam/rmgr.o access/transam/slru.o access/transam/subtrans.o access/transam/multixact.o access/transam/twophase.o access/transam/twophase_rmgr.o access/transam/gtm.o access/gin/ginutil.o access/gin/gininsert.o access/gin/ginxlog.o access/gin/ginentrypage.o access/gin/gindatapage.o access/gin/ginbtree.o access/gin/ginscan.o access/gin/ginget.o access/gin/ginvacuum.o access/gin/ginarrayproc.o access/gin/ginbulk.o access/gin/ginfast.o bootstrap/bootparse.o bootstrap/bootstrap.o catalog/catalog.o catalog/dependency.o catalog/heap.o catalog/index.o catalog/indexing.o catalog/namespace.o catalog/aclchk.o catalog/pg_aggregate.o catalog/pg_constraint.o catalog/pg_conversion.o catalog/pg_depend.o catalog/pg_enum.o catalog/pg_inherits.o catalog/pg_largeobject.o catalog/pg_namespace.o catalog/pg_operator.o catalog/pg_proc.o catalog/pg_shdepend.o catalog/pg_type.o catalog/pgxc_class.o catalog/storage.o catalog/toasting.o parser/analyze.o parser/gram.o parser/keywords.o parser/parser.o parser/parse_agg.o parser/parse_cte.o parser/parse_clause.o parser/parse_expr.o parser/parse_func.o parser/parse_node.o parser/parse_oper.o parser/parse_relation.o parser/parse_type.o parser/parse_coerce.o parser/parse_target.o parser/parse_utilcmd.o parser/scansup.o parser/kwlookup.o commands/aggregatecmds.o commands/alter.o commands/analyze.o commands/async.o commands/cluster.o commands/comment.o commands/conversioncmds.o commands/copy.o commands/dbcommands.o commands/define.o commands/discard.o commands/explain.o commands/foreigncmds.o commands/functioncmds.o commands/indexcmds.o commands/lockcmds.o commands/operatorcmds.o commands/opclasscmds.o commands/portalcmds.o commands/prepare.o commands/proclang.o commands/schemacmds.o commands/sequence.o commands/tablecmds.o commands/tablespace.o commands/trigger.o commands/tsearchcmds.o commands/typecmds.o commands/user.o commands/vacuum.o commands/vacuumlazy.o commands/variable.o commands/view.o executor/execAmi.o executor/execCurrent.o executor/execGrouping.o executor/execJunk.o executor/execMain.o executor/execProcnode.o executor/execQual.o executor/execScan.o executor/execTuples.o executor/execUtils.o executor/functions.o executor/instrument.o executor/nodeAppend.o executor/nodeAgg.o executor/nodeBitmapAnd.o executor/nodeBitmapOr.o executor/nodeBitmapHeapscan.o executor/nodeBitmapIndexscan.o executor/nodeHash.o executor/nodeHashjoin.o executor/nodeIndexscan.o executor/nodeMaterial.o executor/nodeMergejoin.o executor/nodeNestloop.o executor/nodeFunctionscan.o executor/nodeRecursiveunion.o executor/nodeResult.o executor/nodeSeqscan.o executor/nodeSetOp.o executor/nodeSort.o executor/nodeUnique.o executor/nodeValuesscan.o executor/nodeCtescan.o executor/nodeWorktablescan.o executor/nodeLimit.o executor/nodeGroup.o executor/nodeSubplan.o executor/nodeSubqueryscan.o executor/nodeTidscan.o executor/nodeWindowAgg.o executor/tstoreReceiver.o executor/spi.o foreign/foreign.o lib/dllist.o lib/stringinfo.o libpq/be-fsstubs.o libpq/be-secure.o libpq/auth.o libpq/crypt.o libpq/hba.o libpq/ip.o libpq/md5.o libpq/pqcomm.o libpq/pqformat.o libpq/pqsignal.o pgxc/locator/locator.o pgxc/plan/planner.o pgxc/pool/pgxcnode.o pgxc/pool/execRemote.o pgxc/pool/poolmgr.o pgxc/pool/poolcomm.o pgxc/pool/postgresql_fdw.o main/main.o nodes/nodeFuncs.o nodes/nodes.o nodes/list.o nodes/bitmapset.o nodes/tidbitmap.o nodes/copyfuncs.o nodes/equalfuncs.o nodes/makefuncs.o nodes/outfuncs.o nodes/readfuncs.o nodes/print.o nodes/read.o nodes/params.o nodes/value.o optimizer/geqo/geqo_copy.o optimizer/geqo/geqo_eval.o optimizer/geqo/geqo_main.o optimizer/geqo/geqo_misc.o optimizer/geqo/geqo_mutation.o optimizer/geqo/geqo_pool.o optimizer/geqo/geqo_recombination.o optimizer/geqo/geqo_selection.o optimizer/geqo/geqo_erx.o optimizer/geqo/geqo_pmx.o optimizer/geqo/geqo_cx.o optimizer/geqo/geqo_px.o optimizer/geqo/geqo_ox1.o optimizer/geqo/geqo_ox2.o optimizer/path/allpaths.o optimizer/path/clausesel.o optimizer/path/costsize.o optimizer/path/equivclass.o optimizer/path/indxpath.o optimizer/path/joinpath.o optimizer/path/joinrels.o optimizer/path/orindxpath.o optimizer/path/pathkeys.o optimizer/path/tidpath.o optimizer/plan/createplan.o optimizer/plan/initsplan.o optimizer/plan/planagg.o optimizer/plan/planmain.o optimizer/plan/planner.o optimizer/plan/setrefs.o optimizer/plan/subselect.o optimizer/prep/prepjointree.o optimizer/prep/prepqual.o optimizer/prep/preptlist.o optimizer/prep/prepunion.o optimizer/util/clauses.o optimizer/util/joininfo.o optimizer/util/pathnode.o optimizer/util/placeholder.o optimizer/util/plancat.o optimizer/util/predtest.o optimizer/util/relnode.o optimizer/util/restrictinfo.o optimizer/util/tlist.o optimizer/util/var.o port/dynloader.o port/pg_sema.o port/pg_shmem.o postmaster/autovacuum.o postmaster/bgwriter.o postmaster/fork_process.o postmaster/pgarch.o postmaster/pgstat.o postmaster/postmaster.o postmaster/syslogger.o postmaster/walwriter.o regex/regcomp.o regex/regerror.o regex/regexec.o regex/regfree.o rewrite/rewriteRemove.o rewrite/rewriteDefine.o rewrite/rewriteHandler.o rewrite/rewriteManip.o rewrite/rewriteSupport.o storage/buffer/buf_table.o storage/buffer/buf_init.o storage/buffer/bufmgr.o storage/buffer/freelist.o storage/buffer/localbuf.o storage/file/fd.o storage/file/buffile.o storage/freespace/freespace.o storage/freespace/fsmpage.o storage/freespace/indexfsm.o storage/ipc/ipc.o storage/ipc/ipci.o storage/ipc/pmsignal.o storage/ipc/procarray.o storage/ipc/shmem.o storage/ipc/shmqueue.o storage/ipc/sinval.o storage/ipc/sinvaladt.o storage/large_object/inv_api.o storage/lmgr/lmgr.o storage/lmgr/lock.o storage/lmgr/proc.o storage/lmgr/deadlock.o storage/lmgr/lwlock.o storage/lmgr/spin.o storage/lmgr/s_lock.o storage/page/bufpage.o storage/page/itemptr.o storage/smgr/md.o storage/smgr/smgr.o storage/smgr/smgrtype.o tcop/dest.o tcop/fastpath.o tcop/postgres.o tcop/pquery.o tcop/utility.o tsearch/ts_locale.o tsearch/ts_parse.o tsearch/wparser.o tsearch/wparser_def.o tsearch/dict.o tsearch/dict_simple.o tsearch/dict_synonym.o tsearch/dict_thesaurus.o tsearch/dict_ispell.o tsearch/regis.o tsearch/spell.o tsearch/to_tsany.o tsearch/ts_selfuncs.o tsearch/ts_typanalyze.o tsearch/ts_utils.o utils/adt/acl.o utils/adt/arrayfuncs.o utils/adt/array_userfuncs.o utils/adt/arrayutils.o utils/adt/bool.o utils/adt/cash.o utils/adt/char.o utils/adt/date.o utils/adt/datetime.o utils/adt/datum.o utils/adt/domains.o utils/adt/enum.o utils/adt/float.o utils/adt/format_type.o utils/adt/geo_ops.o utils/adt/geo_selfuncs.o utils/adt/int.o utils/adt/int8.o utils/adt/like.o utils/adt/lockfuncs.o utils/adt/misc.o utils/adt/nabstime.o utils/adt/name.o utils/adt/numeric.o utils/adt/numutils.o utils/adt/oid.o utils/adt/oracle_compat.o utils/adt/pseudotypes.o utils/adt/rowtypes.o utils/adt/regexp.o utils/adt/regproc.o utils/adt/ruleutils.o utils/adt/selfuncs.o utils/adt/tid.o utils/adt/timestamp.o utils/adt/varbit.o utils/adt/varchar.o utils/adt/varlena.o utils/adt/version.o utils/adt/xid.o utils/adt/network.o utils/adt/mac.o utils/adt/inet_net_ntop.o utils/adt/inet_net_pton.o utils/adt/ri_triggers.o utils/adt/pg_lzcompress.o utils/adt/pg_locale.o utils/adt/formatting.o utils/adt/ascii.o utils/adt/quote.o utils/adt/pgstatfuncs.o utils/adt/encode.o utils/adt/dbsize.o utils/adt/genfile.o utils/adt/trigfuncs.o utils/adt/tsginidx.o utils/adt/tsgistidx.o utils/adt/tsquery.o utils/adt/tsquery_cleanup.o utils/adt/tsquery_gist.o utils/adt/tsquery_op.o utils/adt/tsquery_rewrite.o utils/adt/tsquery_util.o utils/adt/tsrank.o utils/adt/tsvector.o utils/adt/tsvector_op.o utils/adt/tsvector_parser.o utils/adt/txid.o utils/adt/uuid.o utils/adt/windowfuncs.o utils/adt/xml.o utils/cache/catcache.o utils/cache/inval.o utils/cache/plancache.o utils/cache/relcache.o utils/cache/syscache.o utils/cache/lsyscache.o utils/cache/typcache.o utils/cache/ts_cache.o utils/error/assert.o utils/error/elog.o utils/fmgr/dfmgr.o utils/fmgr/fmgr.o utils/fmgr/funcapi.o utils/hash/dynahash.o utils/hash/hashfn.o utils/hash/pg_crc.o utils/init/flatfiles.o utils/init/globals.o utils/init/miscinit.o utils/init/postinit.o utils/mb/encnames.o utils/mb/conv.o utils/mb/mbutils.o utils/mb/wchar.o utils/mb/wstrcmp.o utils/mb/wstrncmp.o utils/misc/guc.o utils/misc/help_config.o utils/misc/pg_rusage.o utils/misc/ps_status.o utils/misc/superuser.o utils/misc/tzparser.o utils/mmgr/aset.o utils/mmgr/mcxt.o utils/mmgr/portalmem.o utils/resowner/resowner.o utils/sort/logtape.o utils/sort/tuplesort.o utils/sort/tuplestore.o utils/time/combocid.o utils/time/tqual.o utils/time/snapmgr.o utils/fmgrtab.o ../../src/timezone/localtime.o ../../src/timezone/strftime.o ../../src/timezone/pgtz.o utils/probes.o ../../src/interfaces/libpq/fe-connect.o ../../src/interfaces/libpq/fe-secure.o ../../src/interfaces/libpq/fe-misc.o ../../src/interfaces/libpq/fe-protocol3.o ../../src/interfaces/libpq/fe-protocol2.o ../../src/interfaces/libpq/fe-exec.o ../../src/interfaces/libpq/fe-auth.o ../../src/interfaces/libpq/pqexpbuffer.o ../../src/port/libpgport_srv.a ../../src/gtm/client/libgtmclient.a ../../src/gtm/common/libgtm.a ../../src/gtm/libpq/libpqcomm.a -lxslt -lxml2 -lpam -lssl -lcrypto -lkrb5 -lcom_err -lgssapi_krb5 -lcrypt -ldl -lm -lldap -o postgres /usr/bin/ld: ../../src/interfaces/libpq/fe-secure.o: undefined reference to symbol 'pthread_sigmask@@GLIBC_2.2.5' /usr/bin/ld: note: 'pthread_sigmask@@GLIBC_2.2.5' is defined in DSO /lib64/libpthread.so.0 so try adding it to the linker command line /lib64/libpthread.so.0: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [postgres] Error 1 RHEL 5 (GCC 4.1.2, 32 bit) make[4]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/interfaces/libpq' cat: ../../src/interfaces/libpq/objfiles.txt: No such file or directory gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -DPGXC -DPGXC -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -fwrapv -L../../src/port -L/usr/lib -L/usr/lib -L../../src/gtm/libpg -Wl,-E access/common/heaptuple.o access/common/indextuple.o access/common/printtup.o access/common/reloptions.o access/common/scankey.o access/common/tupdesc.o access/gist/gist.o access/gist/gistutil.o access/gist/gistxlog.o access/gist/gistvacuum.o access/gist/gistget.o access/gist/gistscan.o access/gist/gistproc.o access/gist/gistsplit.o access/hash/hash.o access/hash/hashfunc.o access/hash/hashinsert.o access/hash/hashovfl.o access/hash/hashpage.o access/hash/hashscan.o access/hash/hashsearch.o access/hash/hashsort.o access/hash/hashutil.o access/heap/heapam.o access/heap/hio.o access/heap/pruneheap.o access/heap/rewriteheap.o access/heap/syncscan.o access/heap/tuptoaster.o access/heap/visibilitymap.o access/index/genam.o access/index/indexam.o access/nbtree/nbtcompare.o access/nbtree/nbtinsert.o access/nbtree/nbtpage.o access/nbtree/nbtree.o access/nbtree/nbtsearch.o access/nbtree/nbtutils.o access/nbtree/nbtsort.o access/nbtree/nbtxlog.o access/transam/clog.o access/transam/transam.o access/transam/varsup.o access/transam/xact.o access/transam/xlog.o access/transam/xlogutils.o access/transam/rmgr.o access/transam/slru.o access/transam/subtrans.o access/transam/multixact.o access/transam/twophase.o access/transam/twophase_rmgr.o access/transam/gtm.o access/gin/ginutil.o access/gin/gininsert.o access/gin/ginxlog.o access/gin/ginentrypage.o access/gin/gindatapage.o access/gin/ginbtree.o access/gin/ginscan.o access/gin/ginget.o access/gin/ginvacuum.o access/gin/ginarrayproc.o access/gin/ginbulk.o access/gin/ginfast.o bootstrap/bootparse.o bootstrap/bootstrap.o catalog/catalog.o catalog/dependency.o catalog/heap.o catalog/index.o catalog/indexing.o catalog/namespace.o catalog/aclchk.o catalog/pg_aggregate.o catalog/pg_constraint.o catalog/pg_conversion.o catalog/pg_depend.o catalog/pg_enum.o catalog/pg_inherits.o catalog/pg_largeobject.o catalog/pg_namespace.o catalog/pg_operator.o catalog/pg_proc.o catalog/pg_shdepend.o catalog/pg_type.o catalog/pgxc_class.o catalog/storage.o catalog/toasting.o parser/analyze.o parser/gram.o parser/keywords.o parser/parser.o parser/parse_agg.o parser/parse_cte.o parser/parse_clause.o parser/parse_expr.o parser/parse_func.o parser/parse_node.o parser/parse_oper.o parser/parse_relation.o parser/parse_type.o parser/parse_coerce.o parser/parse_target.o parser/parse_utilcmd.o parser/scansup.o parser/kwlookup.o commands/aggregatecmds.o commands/alter.o commands/analyze.o commands/async.o commands/cluster.o commands/comment.o commands/conversioncmds.o commands/copy.o commands/dbcommands.o commands/define.o commands/discard.o commands/explain.o commands/foreigncmds.o commands/functioncmds.o commands/indexcmds.o commands/lockcmds.o commands/operatorcmds.o commands/opclasscmds.o commands/portalcmds.o commands/prepare.o commands/proclang.o commands/schemacmds.o commands/sequence.o commands/tablecmds.o commands/tablespace.o commands/trigger.o commands/tsearchcmds.o commands/typecmds.o commands/user.o commands/vacuum.o commands/vacuumlazy.o commands/variable.o commands/view.o executor/execAmi.o executor/execCurrent.o executor/execGrouping.o executor/execJunk.o executor/execMain.o executor/execProcnode.o executor/execQual.o executor/execScan.o executor/execTuples.o executor/execUtils.o executor/functions.o executor/instrument.o executor/nodeAppend.o executor/nodeAgg.o executor/nodeBitmapAnd.o executor/nodeBitmapOr.o executor/nodeBitmapHeapscan.o executor/nodeBitmapIndexscan.o executor/nodeHash.o executor/nodeHashjoin.o executor/nodeIndexscan.o executor/nodeMaterial.o executor/nodeMergejoin.o executor/nodeNestloop.o executor/nodeFunctionscan.o executor/nodeRecursiveunion.o executor/nodeResult.o executor/nodeSeqscan.o executor/nodeSetOp.o executor/nodeSort.o executor/nodeUnique.o executor/nodeValuesscan.o executor/nodeCtescan.o executor/nodeWorktablescan.o executor/nodeLimit.o executor/nodeGroup.o executor/nodeSubplan.o executor/nodeSubqueryscan.o executor/nodeTidscan.o executor/nodeWindowAgg.o executor/tstoreReceiver.o executor/spi.o foreign/foreign.o lib/dllist.o lib/stringinfo.o libpq/be-fsstubs.o libpq/be-secure.o libpq/auth.o libpq/crypt.o libpq/hba.o libpq/ip.o libpq/md5.o libpq/pqcomm.o libpq/pqformat.o libpq/pqsignal.o pgxc/locator/locator.o pgxc/plan/planner.o pgxc/pool/pgxcnode.o pgxc/pool/execRemote.o pgxc/pool/poolmgr.o pgxc/pool/poolcomm.o pgxc/pool/postgresql_fdw.o main/main.o nodes/nodeFuncs.o nodes/nodes.o nodes/list.o nodes/bitmapset.o nodes/tidbitmap.o nodes/copyfuncs.o nodes/equalfuncs.o nodes/makefuncs.o nodes/outfuncs.o nodes/readfuncs.o nodes/print.o nodes/read.o nodes/params.o nodes/value.o optimizer/geqo/geqo_copy.o optimizer/geqo/geqo_eval.o optimizer/geqo/geqo_main.o optimizer/geqo/geqo_misc.o optimizer/geqo/geqo_mutation.o optimizer/geqo/geqo_pool.o optimizer/geqo/geqo_recombination.o optimizer/geqo/geqo_selection.o optimizer/geqo/geqo_erx.o optimizer/geqo/geqo_pmx.o optimizer/geqo/geqo_cx.o optimizer/geqo/geqo_px.o optimizer/geqo/geqo_ox1.o optimizer/geqo/geqo_ox2.o optimizer/path/allpaths.o optimizer/path/clausesel.o optimizer/path/costsize.o optimizer/path/equivclass.o optimizer/path/indxpath.o optimizer/path/joinpath.o optimizer/path/joinrels.o optimizer/path/orindxpath.o optimizer/path/pathkeys.o optimizer/path/tidpath.o optimizer/plan/createplan.o optimizer/plan/initsplan.o optimizer/plan/planagg.o optimizer/plan/planmain.o optimizer/plan/planner.o optimizer/plan/setrefs.o optimizer/plan/subselect.o optimizer/prep/prepjointree.o optimizer/prep/prepqual.o optimizer/prep/preptlist.o optimizer/prep/prepunion.o optimizer/util/clauses.o optimizer/util/joininfo.o optimizer/util/pathnode.o optimizer/util/placeholder.o optimizer/util/plancat.o optimizer/util/predtest.o optimizer/util/relnode.o optimizer/util/restrictinfo.o optimizer/util/tlist.o optimizer/util/var.o port/dynloader.o port/pg_sema.o port/pg_shmem.o postmaster/autovacuum.o postmaster/bgwriter.o postmaster/fork_process.o postmaster/pgarch.o postmaster/pgstat.o postmaster/postmaster.o postmaster/syslogger.o postmaster/walwriter.o regex/regcomp.o regex/regerror.o regex/regexec.o regex/regfree.o rewrite/rewriteRemove.o rewrite/rewriteDefine.o rewrite/rewriteHandler.o rewrite/rewriteManip.o rewrite/rewriteSupport.o storage/buffer/buf_table.o storage/buffer/buf_init.o storage/buffer/bufmgr.o storage/buffer/freelist.o storage/buffer/localbuf.o storage/file/fd.o storage/file/buffile.o storage/freespace/freespace.o storage/freespace/fsmpage.o storage/freespace/indexfsm.o storage/ipc/ipc.o storage/ipc/ipci.o storage/ipc/pmsignal.o storage/ipc/procarray.o storage/ipc/shmem.o storage/ipc/shmqueue.o storage/ipc/sinval.o storage/ipc/sinvaladt.o storage/large_object/inv_api.o storage/lmgr/lmgr.o storage/lmgr/lock.o storage/lmgr/proc.o storage/lmgr/deadlock.o storage/lmgr/lwlock.o storage/lmgr/spin.o storage/lmgr/s_lock.o storage/page/bufpage.o storage/page/itemptr.o storage/smgr/md.o storage/smgr/smgr.o storage/smgr/smgrtype.o tcop/dest.o tcop/fastpath.o tcop/postgres.o tcop/pquery.o tcop/utility.o tsearch/ts_locale.o tsearch/ts_parse.o tsearch/wparser.o tsearch/wparser_def.o tsearch/dict.o tsearch/dict_simple.o tsearch/dict_synonym.o tsearch/dict_thesaurus.o tsearch/dict_ispell.o tsearch/regis.o tsearch/spell.o tsearch/to_tsany.o tsearch/ts_selfuncs.o tsearch/ts_typanalyze.o tsearch/ts_utils.o utils/adt/acl.o utils/adt/arrayfuncs.o utils/adt/array_userfuncs.o utils/adt/arrayutils.o utils/adt/bool.o utils/adt/cash.o utils/adt/char.o utils/adt/date.o utils/adt/datetime.o utils/adt/datum.o utils/adt/domains.o utils/adt/enum.o utils/adt/float.o utils/adt/format_type.o utils/adt/geo_ops.o utils/adt/geo_selfuncs.o utils/adt/int.o utils/adt/int8.o utils/adt/like.o utils/adt/lockfuncs.o utils/adt/misc.o utils/adt/nabstime.o utils/adt/name.o utils/adt/numeric.o utils/adt/numutils.o utils/adt/oid.o utils/adt/oracle_compat.o utils/adt/pseudotypes.o utils/adt/rowtypes.o utils/adt/regexp.o utils/adt/regproc.o utils/adt/ruleutils.o utils/adt/selfuncs.o utils/adt/tid.o utils/adt/timestamp.o utils/adt/varbit.o utils/adt/varchar.o utils/adt/varlena.o utils/adt/version.o utils/adt/xid.o utils/adt/network.o utils/adt/mac.o utils/adt/inet_net_ntop.o utils/adt/inet_net_pton.o utils/adt/ri_triggers.o utils/adt/pg_lzcompress.o utils/adt/pg_locale.o utils/adt/formatting.o utils/adt/ascii.o utils/adt/quote.o utils/adt/pgstatfuncs.o utils/adt/encode.o utils/adt/dbsize.o utils/adt/genfile.o utils/adt/trigfuncs.o utils/adt/tsginidx.o utils/adt/tsgistidx.o utils/adt/tsquery.o utils/adt/tsquery_cleanup.o utils/adt/tsquery_gist.o utils/adt/tsquery_op.o utils/adt/tsquery_rewrite.o utils/adt/tsquery_util.o utils/adt/tsrank.o utils/adt/tsvector.o utils/adt/tsvector_op.o utils/adt/tsvector_parser.o utils/adt/txid.o utils/adt/uuid.o utils/adt/windowfuncs.o utils/adt/xml.o utils/cache/catcache.o utils/cache/inval.o utils/cache/plancache.o utils/cache/relcache.o utils/cache/syscache.o utils/cache/lsyscache.o utils/cache/typcache.o utils/cache/ts_cache.o utils/error/assert.o utils/error/elog.o utils/fmgr/dfmgr.o utils/fmgr/fmgr.o utils/fmgr/funcapi.o utils/hash/dynahash.o utils/hash/hashfn.o utils/hash/pg_crc.o utils/init/flatfiles.o utils/init/globals.o utils/init/miscinit.o utils/init/postinit.o utils/mb/encnames.o utils/mb/conv.o utils/mb/mbutils.o utils/mb/wchar.o utils/mb/wstrcmp.o utils/mb/wstrncmp.o utils/misc/guc.o utils/misc/help_config.o utils/misc/pg_rusage.o utils/misc/ps_status.o utils/misc/superuser.o utils/misc/tzparser.o utils/mmgr/aset.o utils/mmgr/mcxt.o utils/mmgr/portalmem.o utils/resowner/resowner.o utils/sort/logtape.o utils/sort/tuplesort.o utils/sort/tuplestore.o utils/time/combocid.o utils/time/tqual.o utils/time/snapmgr.o utils/fmgrtab.o ../../src/timezone/localtime.o ../../src/timezone/strftime.o ../../src/timezone/pgtz.o ../../src/interfaces/libpq/fe-connect.o ../../src/interfaces/libpq/fe-secure.o ../../src/interfaces/libpq/fe-misc.o ../../src/interfaces/libpq/fe-protocol3.o ../../src/interfaces/libpq/fe-protocol2.o ../../src/interfaces/libpq/fe-exec.o ../../src/interfaces/libpq/fe-auth.o ../../src/interfaces/libpq/pqexpbuffer.o ../../src/port/libpgport_srv.a ../../src/gtm/client/libgtmclient.a ../../src/gtm/common/libgtm.a ../../src/gtm/libpq/libpqcomm.a -lxslt -lxml2 -lpam -lssl -lcrypto -lgssapi_krb5 -lcrypt -ldl -lm -lldap -o postgres ../../src/interfaces/libpq/fe-secure.o: In function `pq_reset_sigpipe': /var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/interfaces/libpq/fe-secure.c:1413: undefined reference to `pthread_sigmask' ../../src/interfaces/libpq/fe-secure.o: In function `pq_block_sigpipe': /var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/interfaces/libpq/fe-secure.c:1350: undefined reference to `pthread_sigmask' collect2: ld returned 1 exit status make[3]: *** [postgres] Error 1 make[3]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src/backend' make[2]: *** [all] Error 2 make[2]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/lib/pgsql/svn/repo/rpm/redhat/8.4/postgres-xc/EL-5/pgxc' error: Bad exit status from /var/tmp/rpm-tmp.79960 (%build) Regards, -- Devrim GÜNDÜZ PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer PostgreSQL RPM Repository: http://yum.pgrpms.org Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz |
|
From: Mason S. <mas...@en...> - 2010-12-01 14:59:25
|
Benny, Is this with or without the prepared statement patch applied that Andrei posted to the developer mailing list? Thanks, Mason On 12/1/10 12:47 AM, xiong wang wrote: > Dears, > template1=# prepare a(int) as insert into t values($1); > LOG: statement: prepare a(int) as insert into t values($1); > 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 26936) was terminated by signal 11: Segmentation fault > LOG: terminating any other active server processes > 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. > 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. > Regards, > Benny > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App& Earn a Chance To Win $500! > Tap into the largest installed PC base& get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-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: Pavan D. <pav...@gm...> - 2010-12-01 12:54:03
|
On Tue, Nov 30, 2010 at 2:49 PM, xiong wang <wan...@gm...> wrote: > Dears, > > There is a bug in gtm_ctl.c. The varible gtm_path doesn't have enough space > to concat varible gtm_app. > > The enclosure is the patch. > > Hi Benny, Thanks for the patch. We could just use the stack variable instead of allocating memory. I also noticed that we should better be cautious about buffer overflow while constructing the command string. So I added checks to guard against that. While looking at compiler warnings, I also noticed couple of other issues, especially with uninitialized vars. Please see attached patch. I would commit this barring any objections. Thanks, Pavan -- Pavan Deolasee EnterpriseDB http://www.enterprisedb.com |
|
From: sch19831106 <sch...@16...> - 2010-12-01 10:50:56
|
Hi developers. Excuse me! I am shen changhai. ***************************** postgres-xc Environment ******************************** Executed statement " create aggregate " on the postgres-xc,statement and results are as follows: Statement: create aggregate newavg2 (sfunc = int4pl, basetype = int4,stype = int4,finalfunc = int2um, initcond = '0'); Results: ERROR: aggregate ctype must be specified ******************************* pg Environment *********************************** Executed statement " create aggregate " on the pg,statement and results are as follows: Statement: create aggregate newavg2 (sfunc = int4pl, basetype = int4,stype = int4,finalfunc = int2um, initcond = '0'); Results: ERROR: function int2um(integer) does not exist The above results are correct? Thanks! ********************** shen changhai Email: sch...@16... |
|
From: xiong w. <wan...@gm...> - 2010-12-01 08:01:44
|
Hi Michael,
Program terminated with signal 11, Segmentation fault.
[New process 13307]
#0 0x00000000007984e2 in MemoryContextStrdup (context=0x19dac58,
string=0x0) at mcxt.c:659
659 Size len = strlen(string) + 1;
(gdb) bt
#0 0x00000000007984e2 in MemoryContextStrdup (context=0x19dac58,
string=0x0) at mcxt.c:659
#1 0x00000000005c708b in pgxc_planner (query=0x19bc010, cursorOptions=0,
boundParams=0x0) at planner.c:2567
#2 0x00000000006263cb in planner (parse=0x19bc010, cursorOptions=0,
boundParams=0x0) at planner.c:132
#3 0x00000000006887e7 in pg_plan_query (querytree=0x19bc010,
cursorOptions=0, boundParams=0x0) at postgres.c:744
#4 0x0000000000688895 in pg_plan_queries (querytrees=0x19bc940,
cursorOptions=0, boundParams=0x0) at postgres.c:803
#5 0x000000000054f16b in PrepareQuery (stmt=0x199f4f0,
queryString=0x199e890 "prepare a(int) as insert into t values($1);") at
prepare.c:148
#6 0x0000000000690958 in ProcessUtility (parsetree=0x199f4f0,
queryString=0x199e890 "prepare a(int) as insert into t values($1);",
params=0x0, isTopLevel=1 '\001',
dest=0x199f830, completionTag=0x7fff7014f9e0 "") at utility.c:717
#7 0x000000000068f19b in PortalRunUtility (portal=0x19fce80,
utilityStmt=0x199f4f0, isTopLevel=1 '\001',
dest=0x199f830, completionTag=0x7fff7014f9e0 "") at pquery.c:1210
#8 0x000000000068f310 in PortalRunMulti (portal=0x19fce80, isTopLevel=1
'\001', dest=0x199f830, altdest=0x199f830,
completionTag=0x7fff7014f9e0 "") at pquery.c:1315
#9 0x000000000068e99b in PortalRun (portal=0x19fce80,
count=9223372036854775807, isTopLevel=1 '\001',
dest=0x199f830, altdest=0x199f830, completionTag=0x7fff7014f9e0 "") at
pquery.c:837
#10 0x0000000000688c76 in exec_simple_query (query_string=0x199e890 "prepare
a(int) as insert into t values($1);")
at postgres.c:1053
#11 0x000000000068cbe4 in PostgresMain (argc=4, argv=0x18fa170,
username=0x18fa130 "postgres") at postgres.c:3766
#12 0x00000000006555da in BackendRun (port=0x1903480) at postmaster.c:3607
#13 0x0000000000654b37 in BackendStartup (port=0x1903480) at
postmaster.c:3216
#14 0x0000000000651f02 in ServerLoop () at postmaster.c:1445
#15 0x00000000006516a8 in PostmasterMain (argc=7, argv=0x18f8700) at
postmaster.c:1098
#16 0x00000000005d8f47 in main (argc=7, argv=0x18f8700) at main.c:188
Regards,
Benny
2010/12/1 Michael Paquier <mic...@gm...>
> Could you compile with debug mode allowed (--enable-debug when launching
> ./configure)?
> This will help developers tracking easily the error that happened.
>
> Thanks,
> --
> Michael Paquier
> http://michaelpq.users.sourceforge.net
>
>
|
|
From: Koichi S. <koi...@gm...> - 2010-12-01 07:55:43
|
Wang-san; Thanks a lot for the info. Core file will contain the context of pgxc_planner(), which will be needed to find the fix. Andrei; Mason; Could you look into the core file? Regards; ---------- Koichi Suzuki 2010/12/1 xiong wang <wan...@gm...>: > Hi, Koichi, > core stack: > #0 0x00000000007984e2 in MemoryContextStrdup () > (gdb) bt > #0 0x00000000007984e2 in MemoryContextStrdup () > #1 0x00000000005c708b in pgxc_planner () > #2 0x00000000006263cb in planner () > #3 0x00000000006887e7 in pg_plan_query () > #4 0x0000000000688895 in pg_plan_queries () > #5 0x000000000054f16b in PrepareQuery () > #6 0x0000000000690958 in ProcessUtility () > #7 0x000000000068f19b in PortalRunUtility () > #8 0x000000000068f310 in PortalRunMulti () > #9 0x000000000068e99b in PortalRun () > #10 0x0000000000688c76 in exec_simple_query () > #11 0x000000000068cbe4 in PostgresMain () > #12 0x00000000006555da in BackendRun () > #13 0x0000000000654b37 in BackendStartup () > #14 0x0000000000651f02 in ServerLoop () > #15 0x00000000006516a8 in PostmasterMain () > #16 0x00000000005d8f47 in main () > > Regards, > Benny > 2010/12/1 Koichi Suzuki <ko...@in...> >> >> Do you have backtrace list of the backend? I hope SEGV may have created >> core file. >> >> Regards; >> --- >> Koichi Suzuki >> >> (2010年12月01日 14:47), xiong wang wrote: >>> >>> Dears, >>> template1=# prepare a(int) as insert into t values($1); >>> LOG: statement: prepare a(int) as insert into t values($1); >>> 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 26936) was terminated by signal 11: Segmentation fault >>> LOG: terminating any other active server processes >>> 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. >>> 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. >>> Regards, >>> Benny >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Increase Visibility of Your 3D Game App& Earn a Chance To Win $500! >>> Tap into the largest installed PC base& get more eyes on your game by >>> optimizing for Intel(R) Graphics Technology. Get started today with the >>> Intel(R) Software Partner Program. Five $500 cash prizes are up for >>> grabs. >>> http://p.sf.net/sfu/intelisp-dev2dev >>> >>> >>> >>> _______________________________________________ >>> Postgres-xc-developers mailing list >>> Pos...@li... >>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > |
|
From: xiong w. <wan...@gm...> - 2010-12-01 07:50:08
|
Hi, Koichi, core stack: #0 0x00000000007984e2 in MemoryContextStrdup () (gdb) bt #0 0x00000000007984e2 in MemoryContextStrdup () #1 0x00000000005c708b in pgxc_planner () #2 0x00000000006263cb in planner () #3 0x00000000006887e7 in pg_plan_query () #4 0x0000000000688895 in pg_plan_queries () #5 0x000000000054f16b in PrepareQuery () #6 0x0000000000690958 in ProcessUtility () #7 0x000000000068f19b in PortalRunUtility () #8 0x000000000068f310 in PortalRunMulti () #9 0x000000000068e99b in PortalRun () #10 0x0000000000688c76 in exec_simple_query () #11 0x000000000068cbe4 in PostgresMain () #12 0x00000000006555da in BackendRun () #13 0x0000000000654b37 in BackendStartup () #14 0x0000000000651f02 in ServerLoop () #15 0x00000000006516a8 in PostmasterMain () #16 0x00000000005d8f47 in main () Regards, Benny 2010/12/1 Koichi Suzuki <ko...@in...> > Do you have backtrace list of the backend? I hope SEGV may have created > core file. > > Regards; > --- > Koichi Suzuki > > > (2010年12月01日 14:47), xiong wang wrote: > >> Dears, >> template1=# prepare a(int) as insert into t values($1); >> LOG: statement: prepare a(int) as insert into t values($1); >> 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 26936) was terminated by signal 11: Segmentation fault >> LOG: terminating any other active server processes >> 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. >> 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. >> Regards, >> Benny >> >> >> >> >> ------------------------------------------------------------------------------ >> Increase Visibility of Your 3D Game App& Earn a Chance To Win $500! >> Tap into the largest installed PC base& get more eyes on your game by >> optimizing for Intel(R) Graphics Technology. Get started today with the >> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. >> http://p.sf.net/sfu/intelisp-dev2dev >> >> >> >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> > > |
|
From: Koichi S. <ko...@in...> - 2010-12-01 07:04:55
|
Do you have backtrace list of the backend? I hope SEGV may have created core file. Regards; --- Koichi Suzuki (2010年12月01日 14:47), xiong wang wrote: > Dears, > template1=# prepare a(int) as insert into t values($1); > LOG: statement: prepare a(int) as insert into t values($1); > 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 26936) was terminated by signal 11: Segmentation fault > LOG: terminating any other active server processes > 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. > 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. > Regards, > Benny > > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App& Earn a Chance To Win $500! > Tap into the largest installed PC base& get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > > > > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: xiong w. <wan...@gm...> - 2010-12-01 05:48:06
|
Dears, template1=# prepare a(int) as insert into t values($1); LOG: statement: prepare a(int) as insert into t values($1); 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 26936) was terminated by signal 11: Segmentation fault LOG: terminating any other active server processes 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. 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. Regards, Benny |
1 message has been excluded from this view by a project administrator.
