Report proper GUC parameter names in error messages - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Report proper GUC parameter names in error messages
Date
Msg-id CABwTF4X4aD_MT9rAC4E5OyUrXgqC+4cQKeZ4LzJO-VFPoAz_NA@mail.gmail.com
Whole thread Raw
Responses Re: Report proper GUC parameter names in error messages  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Error messages when terminating xlog redo leads the user to believe that there are parameters named max_prepared_xacts and max_locks_per_xact, which is not true. This patch corrects the parameter names emitted in the logs.

Best regards,
--
Gurjeet Singh


Attachment

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Proof of concept: standalone backend with full FE/BE protocol
Next
From: Andrew Dunstan
Date:
Subject: Re: Draft release notes complete