Re: Postgres TR for missing chunk

From: M Tarkeshwar Rao <m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Mithilesh Kumar Gupta" <mithilesh(dot)kumar(dot)gupta(at)ericsson(dot)com>
Subject: Re: Postgres TR for missing chunk
Date: 2014-12-19 09:18:42
Message-ID: 1C16813DAFF3E44B939586605D40E9F011759CE4@ESESSMB107.ericsson.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)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(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2014-12-19 09:30:52 Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps
Previous Message Mark Kirkwood 2014-12-19 08:28:12 Re: Commitfest problems