On Fri, Dec 19, 2014 at 4:18 AM, M Tarkeshwar Rao
wrote:
> 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 info
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 writes:
> You know, that toast table name ringe
Jaime Casanova 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
El dic 16, 2014 1:02 AM, "M Tarkeshwar Rao"
escribió:
>
> Hello Friends,
>
>
>
> Can you please tell me the how can I track the which bugs are fixed in
which release and when they will be fixed,
>
> If I want to track the analysis and status of the bug raised on Postgres.
Can I get this informatio
On Tue, Dec 16, 2014 at 1:02 AM, M Tarkeshwar Rao
wrote:
> Can you please tell me the how can I track the which bugs are fixed in which
> release and when they will be fixed,
We don't have a bug tracker, but you can look at the mailing list
threads and the source code repository.
> BUG #9187: co
Hello Friends,
Can you please tell me the how can I track the which bugs are fixed in which
release and when they will be fixed,
If I want to track the analysis and status of the bug raised on Postgres. Can I
get this information.
>From last few days we are struggling with following issue:
1.
