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:t...@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 <ja...@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.1336019...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers