| From: | Nikhil Ingale <niks(dot)bgm(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Redirect RAISE NOTICE and errors to separate log file |
| Date: | 2023-02-17 17:20:13 |
| Message-ID: | CALXkTpyM1cNwZjQn2WPTm9TkxGJ7nwAzHihUdNnzCEdcP+e3pw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
I'm able to achieve it now. Thank you for the hint David.
On Fri, Feb 17, 2023 at 10:29 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Fri, Feb 17, 2023 at 9:52 AM Nikhil Ingale <niks(dot)bgm(at)gmail(dot)com> wrote:
>
>> I need the non query output in the user defined log file.
>> How can I achieve that?
>>
>
> Learn shell scripting.
>
> At its simplest, have the user replace "/dev/null" in my example with
> whatever path they want.
>
> psql doesn't expose specifying a non-query output channel so you are
> forced to deal with this in a higher/wrapper layer where you can manipulate
> stderr.
>
> David J.
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hotmail | 2023-02-17 17:48:42 | Is it possible to log long running recursive/internal postgresql queries? |
| Previous Message | pradeep pandey | 2023-02-17 17:19:44 | Re: EOL of Pglogical replication support |