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

Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the
Date: 2008-02-26 15:31:40
Message-ID: 47C430DC.3090403@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers

Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>   
>> Am Dienstag, 26. Februar 2008 schrieb Tom Lane:
>>     
>>>> Why should it complain more or less than about the SUBSYS.o
>>>> files?
>>>>         
>>> It has a hard-wired rule not to complain about files named *.o.
>>>       
>
>   
>> Well, we could name the output file SUBSYS.o if that is not too confusing. :)
>>     
>
> Yeah, it probably is.  D'Arcy's suggestion of modifying our
> CVSROOT/cvsignore file seems better.
>
>   

+1. Calling it something like foo.o when it isn't an object file would 
be horrible. This should be a simple one-off operation.

cheers

andrew

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2008-02-26 15:36:16
Subject: Re: Bulk loading performance improvements
Previous:From: Magnus HaganderDate: 2008-02-26 15:28:17
Subject: Re: pg_dump additional options for performance

pgsql-committers by date

Next:From: Peter EisentrautDate: 2008-02-26 15:32:30
Subject: pgsql: Add information about format modifiers that apply to numeric
Previous:From: Tom LaneDate: 2008-02-26 15:12:04
Subject: Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the

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