"Rocco Altier" <RoccoA@Routescape.com> writes:
> Need to have these patches applied to get AIX 5.2 to build as a member
> of the buildfarm.

Er, which buildfarm report is prompting this?

> There are C++ style comments in contrib/pgcrypto which is giving cc
> problems.

Definitely contrary to project policy, will fix.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Tom Lane wrote:

>"Rocco Altier" <RoccoA@Routescape.com> writes:
>
>
>>Need to have these patches applied to get AIX 5.2 to build as a member
>>of the buildfarm.
>>
>>
>
>Er, which buildfarm report is prompting this?
>
>
>

Rocco is probably doing what I normally ask, which is to get builds
working before starting to upload results to the buildfarm server (a
request which is more honored in the breach than the observance).

cheers

andrew

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

Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> Er, which buildfarm report is prompting this?

> Rocco is probably doing what I normally ask, which is to get builds
> working before starting to upload results to the buildfarm server (a
> request which is more honored in the breach than the observance).

Fair enough. But I'm concerned about the proposed patch because it
seems to revert a deliberate change made some time ago:

http://developer.postgresql.org/cvsw....shlib#rev1.65
http://archives.postgresql.org/pgsql...0/msg00054.php

so I think we need more eyeballs on the problem before deciding this is
a good fix.

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

Marko Kreen <marko@l-t.ee> writes:
> On Mon, Jul 18, 2005 at 12:32:21PM -0400, Tom Lane wrote:
>> Definitely contrary to project policy, will fix.

> Don't, they are fixed in "small cleanups" patch that I sent.

Too late, already committed ;-)

I will do something to clean up the mess...

regards, tom lane

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

On Mon, Jul 18, 2005 at 12:32:21PM -0400, Tom Lane wrote:
> "Rocco Altier" <RoccoA@Routescape.com> writes:
> > There are C++ style comments in contrib/pgcrypto which is giving cc
> > problems.
>
> Definitely contrary to project policy, will fix.

Don't, they are fixed in "small cleanups" patch that I sent.

--
marko


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Tom Lane wrote:
> Fair enough. But I'm concerned about the proposed patch because it
> seems to revert a deliberate change made some time ago:
>
> http://developer.postgresql.org/cvsw...kefile.shlib#r
>ev1.65
> http://archives.postgresql.org/pgsql...0/msg00054.php
>
> so I think we need more eyeballs on the problem before deciding this
> is a good fix.

A potentially more correct solution would be to set SHLIB_LINK in the
makefiles of the affected modules only. Certainly we don't want to
link with all libraries all the time.

--
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