Обсуждение: can you please share sample Postgres config file to enable max logging with syslog support?

On 12/18/2014 09:00 PM, M Tarkeshwar Rao wrote:
> Hello friends,
>
> can you please share sample Postgres config file to enable max logging
> with syslog support?
>
> Actually we are facing some issues. We need to enable maximum logging.

Might be better to work this from the other end, as it is easy to drown
in logging information that has nothing to do with the problem.

What are the issues?

>
> Regards
>
> Tarkeshwar
>


--
Adrian Klaver
adrian.klaver@aklaver.com

Hello friends,

 

can you please share sample Postgres config file to enable max logging with syslog support?

 

Actually we are facing some issues. We need to enable maximum logging.

 

The "# ERROR REPORTING AND LOGGING" section in postgresql.conf fairly self-explanatory and commented. To get started just do the following:

Route to syslog:
log_destination = 'syslog'
syslog_facility = 'LOCAL2'
syslog_ident = 'postgres'

(Set facility and ident as appropriate for your syslogging.)

To log all statements:
log_min_duration_statement = 0

There are a number of other things you can log (connections, disconnections, checkpoints, ...) as well as some tweaks you can make to the log formats but it's all laid out in a reasonably straightforward way in the config file.

If you described the issues you are facing the community could offer better advice on what information to capture and possible solutions. The PostgreSQL log is not your only source of troubleshooting information. SAR and other sources of system information can be important as well.

Cheers,
Steve

On 12/21/2014 10:17 PM, M Tarkeshwar Rao wrote:
> ERROR:  missing chunk number 0 for toast value 54787 in pg_toast_2619

this error means you have at least one corrupted file. pg_toast data is
used to store fields too large for simple tuple storage.   a postgres
expert could track down which table this toast value belongs to.

until you fix this, and identify the missing data, you should not do
anything to this database, or risk further data corruption.  in
particular  you won't be able to do the required pg_dumpall that you
need to do a major version upgrade.



--
john r pierce                                      37N 122W
somewhere on the middle of the left coast