| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Dhanaraj(dot)M(at)Sun(dot)COM, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Patch for - Allow server logs to be remotely read |
| Date: | 2006-06-08 14:17:07 |
| Message-ID: | 27165.1149776227@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Is that wrong? Yes. Looking at the C file, I see what you mean. Let
> me update the README.adminpack file. read_file is already in the
> backend code, and was in 8.1.X too.
I wonder if we should take pg_read_file (and the rest of genfile.c)
back out of the backend and stick them into contrib/adminpack. The
argument for having them in the backend was always pretty weak to me.
In particular, a DBA who doesn't want them in his system for security
reasons has no simple way to get rid of them if they're in core, but
not installing a contrib module is easy enough.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-06-08 14:28:02 | Re: Patch for - Allow server logs to be remotely read |
| Previous Message | Bruce Momjian | 2006-06-08 14:15:14 | Re: Patch for - Allow server logs to be remotely read |