Re: [BUGS] osx and thread safety?

2004-08-16 Thread Tom Lane
Theodore Petrosky <[EMAIL PROTECTED]> writes: > I get these errors: > ld: common symbols not allowed with MH_DYLIB output > format with the -multi_module option > fe-secure.o definition of common _thread_in_send (size > 4) Some googling turns up the fact that OS X does not like uninitialized glob

Re: [BUGS] osx and thread safety?

2004-08-16 Thread Bruce Momjian
You need threading if you need to do threads in your client applications. Not sure why you get the link error though. --- Theodore Petrosky wrote: > Can someone shed some light on the thread safety > switch. I am using Post

[BUGS] osx and thread safety?

2004-08-16 Thread Theodore Petrosky
Can someone shed some light on the thread safety switch. I am using PostgreSQL on mac os x. I have made and installed from 7.2 through 8.0b. I now see this feature of thread safety and I don't understand why I would need it. I have tried: ./configure --with-rendezvous --enable-thread-safety I ge

Re: [BUGS] BUG #1208: Invalid page header

2004-08-16 Thread Tom Lane
"Robert E. Bruccoleri" <[EMAIL PROTECTED]> writes: > Question: were there any significant changes made to the > buffer management code between 7.4 and 8.0 that would explain the > difference? There are some nontrivial changes, but none that I would regard as likely to cause a multiprocessing

Re: [BUGS] BUG #1208: Invalid page header

2004-08-16 Thread Robert E. Bruccoleri
Dear All, Thanks for responding. First of all, the Intel compiler does not accept inline assembly code, so I substituted the following compiler intrinsic in its place: #if defined(__ia64__) || defined(__ia64) /* __ia64 used by ICC compiler? */ /* Intel Itanium */ #define HAS_TEST_AND_SET

Re: [BUGS] BUG #1208: Invalid page header

2004-08-16 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> But that code is gcc-only, and he's not using gcc. > I think the icc compiler claims to be gcc-compatible in that area, so > it's quite likely that the gcc assembler code would be used. Oh, good point. In that case it seems entir

Re: [BUGS] BUG #1208: Invalid page header

2004-08-16 Thread Peter Eisentraut
Tom Lane wrote: > But that code is gcc-only, and he's not using gcc. I think the icc compiler claims to be gcc-compatible in that area, so it's quite likely that the gcc assembler code would be used. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end

Re: [BUGS] BUG #1208: Invalid page header

2004-08-16 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > If you are sure your storage and memory are good, I can think of only > > two other ideas. One is a gcc bug. You are running Itanium so it is > > possible. The only other possibility I can think of is that that our > > ia64 assemble

Re: [BUGS] BUG #1208: Invalid page header

2004-08-16 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > If you are sure your storage and memory are good, I can think of only > two other ideas. One is a gcc bug. You are running Itanium so it is > possible. The only other possibility I can think of is that that our > ia64 assembler code is wrong. It is:

Re: [PATCHES] [BUGS] Bug: century/millenium still broken

2004-08-16 Thread Bruce Momjian
Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches It will be applied as soon as one of the PostgreSQL committers reviews and approves it. --- Fa

Re: [BUGS] BUG #1208: Invalid page header

2004-08-16 Thread Bruce Momjian
If you are sure your storage and memory are good, I can think of only two other ideas. One is a gcc bug. You are running Itanium so it is possible. The only other possibility I can think of is that that our ia64 assembler code is wrong. It is: static __inline__ int tas

Re: [BUGS] 8.0 beta1: pg_dump/restore failing

2004-08-16 Thread Tom Lane
Edmund Bacon <[EMAIL PROTECTED]> writes: > The problem is that pg_restore is not correctly recognizing the ending > $$ quotes on functions: This is a known bug. There was a preliminary patch posted for it a couple days ago. regards, tom lane ---(

Re: [BUGS] Turkish downcasting in PL/pgSQL

2004-08-16 Thread Tom Lane
Devrim GUNDUZ <[EMAIL PROTECTED]> writes: > A few minutes before I tried on a Debian unstable, as Nicolai reported. > But all the regression tests passed again, using the latest flex + > glibc... I can't reproduce the problem :( Or there is not a bug :) Hmph. Either Nicolai has a weird locale s

Re: [BUGS] Turkish downcasting in PL/pgSQL

2004-08-16 Thread Devrim GUNDUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Mon, 16 Aug 2004, Tom Lane wrote: > > I'm using the latest tr_TR locale of glibc, and flex-2.5.4a-29 (of RHEL) > > and flex-2.5.4a-31 (of FC 2). > > > What am I missing? > > If you built from a tarball, then the flex run is already done for

Re: [BUGS] Turkish downcasting in PL/pgSQL

2004-08-16 Thread Tom Lane
Devrim GUNDUZ <[EMAIL PROTECTED]> writes: > All 96 tests passed. > I'm using the latest tr_TR locale of glibc, and flex-2.5.4a-29 (of RHEL) > and flex-2.5.4a-31 (of FC 2). > What am I missing? If you built from a tarball, then the flex run is already done for you. Remove src/pl/plpgsql/src/pl_

Re: [BUGS] Turkish downcasting in PL/pgSQL

2004-08-16 Thread Devrim GUNDUZ
Hi, On Thu, 12 Aug 2004, Tom Lane wrote: > > flex (flex version 2.5.4) incorporates case-insensitivity in it's > > state tables because if I run flex stage with LANG=C everything > > works fine. > > Ick. That is of course why it worked for me when I tested it :-( Nicolai is on holiday now.