From: | Tim Holloway <mtsinc(at)southeast(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Logging - pg_options format change? |
Date: | 1999-10-26 00:01:15 |
Message-ID: | 3814EF4B.70023082@southeast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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+
barswitch
dumplevel = 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 1999-10-26 00:59:49 | Re: [HACKERS] Re: [GENERAL] Postgres INSERTs much slower than MySQL? |
Previous Message | Byron Nikolaidis | 1999-10-25 23:36:52 | Re: [HACKERS] Re: [PATCHES] COMMENT ON patch |