| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: serverlog function (log_destination file) |
| Date: | 2004-06-07 14:52:23 |
| Message-ID: | 40C48127.3000706@pse-consulting.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>
>If I were trying to solve Andreas' problem, I'd pipe stderr to some
>program that stores recent log output in a file that I know the location
>of and can read from the hypothetical log-grabber function. Actually I
>don't see that there's any need to involve Postgres itself in this issue
>at all --- seems like the only agreement needed is between the GUI and
>the postmaster launching script about where the log file is.
>
>
What if there's no file access (e.g. only db admin, not sys admin, no
file sharing, firewalled with only 5432 port access or similar)? I'd
like a solution that needs just enabling in postgresql.conf and a button
in pgadmin3 (probably phppgadmin would follow soon), on any platform.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shridhar Daithankar | 2004-06-07 14:52:35 | Re: [pgsql-hackers-win32] Failures with windows port |
| Previous Message | Dave Page | 2004-06-07 14:46:43 | Re: serverlog function (log_destination file) |