Skip site navigation (1) Skip section navigation (2)

Re: BUG #3516: Incomplete #ifdef statement in s_lock.h

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dirk Tilger <dirk(at)miriup(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3516: Incomplete #ifdef statement in s_lock.h
Date: 2007-08-06 15:04:37
Message-ID: 27531.1186412677@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Dirk Tilger <dirk(at)miriup(dot)de> writes:
> FYI: we also apply the attached patch to postgre, so that the 
> 'configure' script would not add the -mp1, when -mp was already 
> specified. From the manual:

There is absolutely no chance that we will accept this patch, as it is
known to break Postgres.

I suggest also that you reconsider the wisdom of using -no-gcc to
compile Postgres, as there are quite a lot of places where we generate
better code if we think it's gcc.  There is no hint in what you showed
that there is any binary compatibility issue between gcc and -no-gcc
modes, so even if you have some other piece of code that fails without
-no-gcc, that's still not a reason to build Postgres that way.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2007-08-06 15:17:40
Subject: Re: BUG #3518: ERROR: IN types character varying and integer cannot be matched
Previous:From: Mouhamadou DIADate: 2007-08-06 14:47:57
Subject: BUG #3519: Postgres takes the wrong query plan resulting in performance issues

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group