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

Re: switch for disabling ecpg & pgeasy

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marko Kreen <marko(at)l-t(dot)ee>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: switch for disabling ecpg & pgeasy
Date: 2001-06-15 18:32:31
Message-ID: 25310.992629951@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Marko Kreen <marko(at)l-t(dot)ee> writes:
> * configure switches for disabling ECPG and libpgeasy
>   compile, as they are not used always

Why bother?  They don't take long to compile, and if we make them
optional they'll just get less testing coverage.  (Admittedly,
finding out whether something compiles doesn't prove it will work,
but it's a lot better than no testing at all.)

More to the point, if we start making bits and pieces optionally
compiled "just because", we will soon have a list of configure options
so long that you can't find the important stuff.  I think we should keep
the configure options to the minimum.

			regards, tom lane

In response to

pgsql-patches by date

Next:From: Marko KreenDate: 2001-06-15 19:35:15
Subject: Re: switch for disabling ecpg & pgeasy
Previous:From: Peter EisentrautDate: 2001-06-15 17:59:08
Subject: Re: switch for disabling ecpg & pgeasy

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