Logging - pg_options format change? - Mailing list pgsql-hackers

From Tim Holloway
Subject Logging - pg_options format change?
Date
Msg-id 3814EF4B.70023082@southeast.net
Whole thread Raw
Responses Re: [HACKERS] Logging - pg_options format change?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Would it be objectionable if I altered the format of the pg_options file slightly?
I feel the need to handle a somewhat more complex syntax for the logging subsystem.

What I'm proposing is to wrap the existing stuff in a backwards-compatible manner,
but extend it. Like so:

---------------------------------------------------
# postgresql options

debugging {fooparam+barswitchdumplevel = 11
}

logging {# details to follow
}
---------------------------------------------------

Also, is YACC sufficently thread-safe that if a SIGHUP starts
parsing options it won't collide with another task's in-progress
parsing of, say a SELECT statement?
  Thanks,
    Tim Holloway


pgsql-hackers by date:

Previous
From: Byron Nikolaidis
Date:
Subject: Re: [HACKERS] Re: [PATCHES] COMMENT ON patch
Next
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] RFC: Industrial-strength logging