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

Re: [COMMITTERS] pgsql: Sigh ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Sigh ...
Date: 2008-05-03 17:17:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackerspgsql-patches
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Peter Eisentraut wrote:
>> Btw., it is quite easily possible to use the autom4te tracing facility to 
>> parse the file, in case you are interested in generating some of 
>> the Windows build code automatically.

> Yeah, maybe. Let's fix the issue pg_config.h.win32 that Tom raised first.

+1 for both.  We really need to eliminate as much redundancy as we can
between the two build systems, because it'll keep biting us until we do.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2008-05-03 17:31:01
Subject: Re: statement timeout vs dump/restore
Previous:From: Tom LaneDate: 2008-05-03 17:01:36
Subject: Re: statement timeout vs dump/restore

pgsql-committers by date

Next:From: User H-saitoDate: 2008-05-03 18:52:06
Subject: psqlodbc - psqlodbc: Adjustment of a library.
Previous:From: User FxjrDate: 2008-05-03 15:33:19
Subject: npgsql - Npgsql2: Added a prepared bytea support test.

pgsql-patches by date

Next:From: Andreas 'ads' ScherbaumDate: 2008-05-03 17:26:12
Subject: Re: configure option for XLOG_BLCKSZ
Previous:From: Tom LaneDate: 2008-05-03 17:14:35
Subject: Re: configure option for XLOG_BLCKSZ

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