I think we have a consensus. Destroy and recreate logging
data structures/tasks on receipt of
suitable event.
For simple things like log levels, though, I'd still like
feedback on
desirablility and feasibility of altering basic logging
options though
(authorized!) frontends. As a user,
Why not do something similar to what we are doing with pg_shadow? If I
remember the logic right, when you update pg_shadow, one ofits "steps" is
to dump it to a text file so that postmaster can read it? this should
make it easy for one user/database to have one logging set, while another
The Hermit Hacker [EMAIL PROTECTED] writes:
Why not do something similar to what we are doing with pg_shadow? If I
remember the logic right, when you update pg_shadow, one ofits "steps" is
to dump it to a text file so that postmaster can read it?
I thought about suggesting that, but IIRC the
On Sat, 23 Oct 1999, Aaron J. Seigo wrote:
There MUST exist a way to alter the logging level on-the-fly;
IMHO this is a rock bottom, non negotiable requirement.
whilst i don't think this is MUST, it is EXTREMELY desirable and would make the
logging actually useful for large installations
The Hermit Hacker wrote:
On Sat, 23 Oct 1999, Aaron J. Seigo wrote:
There MUST exist a way to alter the logging level on-the-fly;
IMHO this is a rock bottom, non negotiable requirement.
whilst i don't think this is MUST, it is EXTREMELY desirable and would make the
logging
