| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Protection of debugging options |
| Date: | 2000-06-07 16:30:42 |
| Message-ID: | Pine.LNX.4.21.0006071825100.16917-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane writes:
> I object loudly --- this would be a major pain in the rear end.
It sure would. But it's a trade off between that and log stuffing, I
suppose.
> Finally, where did you get the idea that the equivalent SET vars should
> be superuser restricted?
Nowhere. The ones that were adopted from pg_options had a general
superuser restriction. Any that might be new just played along. The idea
was to leave it as is at first and then over time look at each option in
detail.
Okay, so all logging/debugging options available to the public.
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-06-07 16:35:49 | Re: day of week |
| Previous Message | Travis Bauer | 2000-06-07 16:09:18 | java settings in emacs for postgres |