Re: Postgres TR for missing chunk - Mailing list pgsql-hackers

From M Tarkeshwar Rao
Subject Re: Postgres TR for missing chunk
Date
Msg-id 1C16813DAFF3E44B939586605D40E9F011759CE4@ESESSMB107.ericsson.se
Whole thread Raw
In response to Re: Postgres TR for missing chunk  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Postgres TR for missing chunk  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hello friends,

Thanks for your useful inputs.

We are facing this issue and want to analyse this through logging.
can you please share a sample Postgres config file to enable max logging with syslog support?

What should be the debug level so that I can capture the failure information?

Regards
Tarkeshwar

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: 16 December 2014 22:25
To: Jaime Casanova
Cc: M Tarkeshwar Rao; PostgreSQL-development
Subject: Re: [HACKERS] Postgres TR for missing chunk

Jaime Casanova <jaime@2ndquadrant.com> writes:
> You know, that toast table name ringed a bell.
> Look at this thread maybe this is your problem, and if it is then is
> already fixed and you should update.
> http://www.postgresql.org/message-id/12138.1336019219@sss.pgh.pa.us

That was about transient failures though, not persistent ones, which is what the OP seems to be claiming he's getting.

> Btw, when giving a bug report you should start but saying your
> PostgreSQL's version and explain what you did based on Google's "wisdom"

Yeah.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: Commitfest problems
Next
From: Petr Jelinek
Date:
Subject: Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps