| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: serverlog function (log_destination file) |
| Date: | 2004-06-07 14:46:43 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4A842@ratbert.vale-housing.co.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 07 June 2004 15:32
> To: Dave Page
> Cc: Andreas Pflug; PostgreSQL Development
> Subject: Re: [HACKERS] serverlog function (log_destination file)
>
>
> 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.
Thanks Tom. I wonder if we (the pgAdmin team) finally need to bite the
proverbial bullet and write a helper daemon that can allow access to
logs as well as config files and pg_ctl etc. as an optional extra
component.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2004-06-07 14:52:23 | Re: serverlog function (log_destination file) |
| Previous Message | Bruno Wolff III | 2004-06-07 14:34:59 | Re: serverlog function |