I am thinking we would need an option at the start like --strict that would throw an error for any later invalid options.
--------------------------------------------------------------------------- Dave Page wrote: > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Marko Kreen > > Sent: 05 May 2006 12:22 > > To: Tom Lane > > Cc: Martijn van Oosterhout; pgsql-patches@postgresql.org > > Subject: Re: [PATCHES] [PATCH] Have configure complain about > > unknown options > > > > As PostgreSQL tree is not set up that way, I think for > > clarity sake it would be better to give explicit errors for > > unknown options. > > > > I'm not in a position to argue about why autoconf works this way, but I > can say that I'd like to see unsupported options rejected if there is a > sensible way to do it. I've been bitten more than once by mistakenly > using --enable-foo rather than --with-foo, or just plain mis-typing. > > Regards, Dave. > > ---------------------------(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 > -- Bruce Momjian http://candle.pha.pa.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
