Bizarre coding in recovery target GUC management - Mailing list pgsql-hackers

From Tom Lane
Subject Bizarre coding in recovery target GUC management
Date
Msg-id 3124549.1602518445@sss.pgh.pa.us
Whole thread Raw
Responses Re: Bizarre coding in recovery target GUC management
List pgsql-hackers
Would someone explain to me why assign_recovery_target_lsn and related GUC
assign hooks throw errors, rather than doing so in the associated check
hooks?  An assign hook is not supposed to throw an error.  Full stop, no
exceptions.  We wouldn't bother to separate those hooks otherwise.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15858: could not stat file - over 4GB
Next
From: Heikki Linnakangas
Date:
Subject: Re: partition routing layering in nodeModifyTable.c