| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: log_destination=file |
| Date: | 2017-09-08 06:58:23 |
| Message-ID: | CA+q6zcUYQmiDejfgzz5+eAPz0b1Zdq-ysUoJAp21BnhTt+x5jw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 8 September 2017 at 01:32, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> 1. where was stderr actually sent? To the console, to /dev/null or to a
file?
To the console (but I can also try other options, although I'm not sure if
it would have any impact).
> 2. Could you run the same thing (on the same machine) with the logging
collector on and logging to file, without the patch? I'd assume that gives
performance similar to running with the patch, but it would be good to
confirm that.
Sure, I'll do it this weekend.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Surafel Temesgen | 2017-09-08 07:25:58 | Re: Support to COMMENT ON DATABASE CURRENT_DATABASE |
| Previous Message | Michael Banck | 2017-09-08 06:41:56 | Re: Create replication slot in pg_basebackup if requested and not yet present |