Postgres Pro
Downloads
Home   >   mailing lists

Re: Simplify backtrace_functions GUC code - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Simplify backtrace_functions GUC code
Date
Msg-id 202403171307.5tkrbcebxuqa@alvherre.pgsql
Whole thread Raw
In response to Simplify backtrace_functions GUC code  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
Tree view 
On 2024-Mar-17, Bharath Rupireddy wrote:

> I think the code can be simplified a bit by using
> SplitIdentifierString like in the attached patch. With this,
> backtrace_function_list variable and assign_backtrace_functions() will
> go away.

Did you read the discussion that led to the current coding?  What part
of it is no longer valid, in such a way that you want to make the code
look like an approach that was rejected back then?


https://www.postgresql.org/message-id/flat/35beac83-bf15-9d79-05c4-2dccd0834993%402ndquadrant.com#4dc9ccec753c0d99369be9d53bf24476

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Make attstattarget nullable
Next
From: Kambam Vinay
Date:
Subject: Re: Fix for timestamp lag issue from emit_log_hook when GUC log_line_prefix has '%m'