Re: recovery.conf parsing problems - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: recovery.conf parsing problems
Date
Msg-id 1166107319.3882.30.camel@silverbirch.site
Whole thread Raw
In response to Re: recovery.conf parsing problems  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: recovery.conf parsing problems  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2006-12-14 at 13:52 +0100, Peter Eisentraut wrote: 
> Simon Riggs wrote:
> > > It would probably be far easier for long-term maintenance if you
> > > just built an independent lexer, instead of trying to make
> > > guc-file.l serve multiple masters.
> >
> > Will do.
> 
> I'm actually not so sure that this is a good idea.  The lexical 
> structure should be exactly the same, and some things like include 
> files might become useful as well, so why should all this be 
> replicated?

I assumed the actual lexer would be the same, just the code that invokes
it would be different. I'm happy to do things either way.

--  Simon Riggs              EnterpriseDB   http://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Operator class group proposal
Next
From: Tom Lane
Date:
Subject: Re: recovery.conf parsing problems