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

From Simon Riggs
Subject Re: recovery.conf parsing problems
Date
Msg-id 1166039531.3733.45.camel@silverbirch.site
Whole thread Raw
In response to Re: recovery.conf parsing problems  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: recovery.conf parsing problems  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: recovery.conf parsing problems  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Wed, 2006-12-13 at 19:28 +0000, Simon Riggs wrote:
> On Wed, 2006-12-13 at 04:23 +0000, Andrew - Supernews wrote:
> > While testing a PITR recovery, I discovered that recovery.conf doesn't
> > seem to allow specifying ' in the command string, making it hard to
> > protect the restore_command against problematic filenames (whitespace
> > etc.). This doesn't seem to be a problem for archive_command, which
> > allows \' (e.g. archive_command = '/path/to/script \'%f\' \'%p\'').

Immediate workaround is to use a script to encapsulate the actual
desired request.

> > Should this be fixed?
> 
> Yes, I'll look into that.

OK, I would propose to extend the guc-file.l to include sufficient code
to allow the parsing of the conf files to be identical between the
postgresql.conf and the recovery.conf (it isn't the same yet).

There'll be care taken to ensure that the various options are not
settable in the wrong file.

Any requests for specific implementation details? I'll be looking to
remove code from xlog.c, if possible.

Implementation won't be immediate because of other current work.

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




pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: EXPLAIN ANALYZE
Next
From: "Simon Riggs"
Date:
Subject: Re: Concurrent connections in psql