Re: Common function for percent placeholder replacement - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Common function for percent placeholder replacement
Date
Msg-id 20230104003700.GB289060@nathanxps13
Whole thread Raw
In response to Re: Common function for percent placeholder replacement  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: Common function for percent placeholder replacement
List pgsql-hackers
In general, +1.

On Tue, Dec 20, 2022 at 06:30:40AM +0100, Peter Eisentraut wrote:
> (Still need to think about Robert's comment about lack of error context.)

Would adding the name of the GUC be sufficient?

    ereport(ERROR,
            (errmsg("could not build %s", guc_name),
             errdetail("string ends unexpectedly after escape character \"%%\"")));

> + * A value may be NULL.  If the corresponding placeholder is found in the
> + * input string, the whole function returns NULL.

This appears to be carried over from BuildRestoreCommand(), and AFAICT it
is only necessary because pg_rewind doesn't support %r in restore_command.
IMHO this behavior is counterintuitive and possibly error-prone and should
result in an ERROR instead.  Since pg_rewind is the only special case, it
could independently check for %r before building the command.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: moving extraUpdatedCols out of RangeTblEntry (into ModifyTable)
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Delay commit status checks until freezing executes.