> -----Original Message-----
> From: Rossi, Maria [mailto:maria.rossi@us.pgds.com]
> Sent: Thursday, March 12, 2015 11:55 AM
> To: Igor Neyman; 'Shreeyansh Dba'; gilberto.castillo@etecsa.cu
> Cc: Postgres Maillist
> Subject: RE: [ADMIN] Errorlog empty
>
> It is 'on'.
>
> postgres=# show logging_collector;
> logging_collector
> -------------------
> on
> (1 row)
>
> postgres=#
>
>
>
> Maria
>
> -----Original Message-----
> From: Igor Neyman [mailto:ineyman@perceptron.com]
> Sent: Thursday, March 12, 2015 11:52 AM
> To: Rossi, Maria; 'Shreeyansh Dba'; gilberto.castillo@etecsa.cu
> Cc: Postgres Maillist
> Subject: RE: [ADMIN] Errorlog empty
>
> From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-
> owner@postgresql.org] On Behalf Of Rossi, Maria
> Sent: Thursday, March 12, 2015 11:29 AM
> To: 'Shreeyansh Dba'; gilberto.castillo@etecsa.cu
> Cc: Postgres Maillist
> Subject: Re: [ADMIN] Errorlog empty
>
> The logging_collector is on, but I don’t know if it was restarted after it was
> turned on. I did run a ‘pg_ctl reload’, but still it did not log any msgs.
> Does it need an actual restart? I cannot simply do that because this is
> production, has to be scheduled.
>
> Thanks.
>
> Maria
>
>
> After ‘pg_ctl reload’ you can check current value of any parameter (including
> logging_collector) by issuing:
>
> Show <parameter_name>
>
> i.e.: show logging_collector;
>
>
> Regards,
> Igor Neyman
What about other parameters?
Log_destination
Log_filename
Log_directory
Log_connections
Log_disconnections
Regards,
Igor Neyman
