Re: BUG #3516: Incomplete #ifdef statement in s_lock.h - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #3516: Incomplete #ifdef statement in s_lock.h
Date
Msg-id 27531.1186412677@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #3516: Incomplete #ifdef statement in s_lock.h  (Dirk Tilger <dirk@miriup.de>)
List pgsql-bugs
Dirk Tilger <dirk@miriup.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

pgsql-bugs by date:

Previous
From: "Mouhamadou DIA"
Date:
Subject: BUG #3519: Postgres takes the wrong query plan resulting in performance issues
Next
From: Tom Lane
Date:
Subject: Re: BUG #3518: ERROR: IN types character varying and integer cannot be matched