Re: [HACKERS] DTrace enabled build fails

2006-07-31 Thread Bruce Momjian
Robert Lor wrote:
 Peter Eisentraut wrote:
 
 That rings a bell.  Can we get a more precise designation on what 
 version of DTrace we support?  And where can one get that required 
 update?
 
   
 
 Peter,
 
 The problem with static function was fixed recently and is now available 
 in Solaris Express (the development version of Solaris). You can get the 
 bits from http://www.sun.com/software/solaris/solaris-express/get.jsp. I 
 forgot to mention this know issue in my previous emails!
 
 I was told by the DTrace engineer that this fix will be in the next 
 update of Solaris 10.

Do we need to add detection logic to catch buggy versions?

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [HACKERS] DTrace enabled build fails

2006-07-31 Thread Robert Lor

Bruce Momjian wrote:



Do we need to add detection logic to catch buggy versions?

 

Instead of adding extra logic, I think it's sufficient with 
documentation since the issue will soon be fixed in the next Solaris update.


Regards,
-Robert

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] DTrace enabled build fails

2006-07-31 Thread Tom Lane
Robert Lor [EMAIL PROTECTED] writes:
 Bruce Momjian wrote:
 Do we need to add detection logic to catch buggy versions?
 
 Instead of adding extra logic, I think it's sufficient with 
 documentation since the issue will soon be fixed in the next Solaris update.

I agree ... it's not like this is a feature aimed at novices.

regards, tom lane

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] DTrace enabled build fails

2006-07-30 Thread Robert Lor

Peter Eisentraut wrote:

That rings a bell.  Can we get a more precise designation on what 
version of DTrace we support?  And where can one get that required 
update?


 


Peter,

The problem with static function was fixed recently and is now available 
in Solaris Express (the development version of Solaris). You can get the 
bits from http://www.sun.com/software/solaris/solaris-express/get.jsp. I 
forgot to mention this know issue in my previous emails!


I was told by the DTrace engineer that this fix will be in the next 
update of Solaris 10.


Regards,
-Robert

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] DTrace enabled build fails

2006-07-29 Thread Peter Eisentraut
Tom Lane wrote:
 Peter Eisentraut [EMAIL PROTECTED] writes:
  Does it not like static functions?

 I seem to recall Robert mentioning that they'd only recently fixed
 DTrace to cope with probes in static functions.  Maybe you need to
 get an update?

That rings a bell.  Can we get a more precise designation on what 
version of DTrace we support?  And where can one get that required 
update?

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly


[HACKERS] DTrace enabled build fails

2006-07-28 Thread Peter Eisentraut
/usr/sbin/dtrace  -G -s utils/probes.d access/SUBSYS.o bootstrap/SUBSYS.o 
catalog/SUBSYS.o parser/SUBSYS.o commands/SUBSYS.o executor/SUBSYS.o 
lib/SUBSYS.o libpq/SUBSYS.o main/SUBSYS.o nodes/SUBSYS.o optimizer/SUBSYS.o 
port/SUBSYS.o postmaster/SUBSYS.o regex/SUBSYS.o rewrite/SUBSYS.o 
storage/SUBSYS.o tcop/SUBSYS.o utils/SUBSYS.o ../../src/timezone/SUBSYS.o -o 
utils/probes.o
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline 
-Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -g 
-L../../src/port -L/opt/csw/lib/ -Wl,-R'/export/home/pei/devel/pg-install/lib'  
access/SUBSYS.o bootstrap/SUBSYS.o catalog/SUBSYS.o parser/SUBSYS.o 
commands/SUBSYS.o executor/SUBSYS.o lib/SUBSYS.o libpq/SUBSYS.o main/SUBSYS.o 
nodes/SUBSYS.o optimizer/SUBSYS.o port/SUBSYS.o postmaster/SUBSYS.o 
regex/SUBSYS.o rewrite/SUBSYS.o storage/SUBSYS.o tcop/SUBSYS.o utils/SUBSYS.o 
../../src/timezone/SUBSYS.o utils/probes.o ../../src/port/libpgport_srv.a -lrt 
-lsocket -lm -o postgres
Undefined   first referenced
 symbol in file
AbortTransactionutils/probes.o
CommitTransaction   utils/probes.o
ld: fatal: Symbol referencing errors. No output written to postgres
collect2: ld returned 1 exit status
gmake: *** [postgres] Error 1

Does it not like static functions?

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Re: [HACKERS] DTrace enabled build fails

2006-07-28 Thread Tom Lane
Peter Eisentraut [EMAIL PROTECTED] writes:
 Does it not like static functions?

I seem to recall Robert mentioning that they'd only recently fixed
DTrace to cope with probes in static functions.  Maybe you need to
get an update?

regards, tom lane

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match