From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Selva manickaraja <mavles78@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: PostgreSQL logs filling up file system due to duplicate key error
Date: Sat, 28 May 2011 07:23:57 -0600
Message-ID: <5C68D2EA-F5DD-4C5B-A5C2-5A5F1DF4A358@elevated-dev.com> (raw)
In-Reply-To: <BANLkTimQ_mqPq0iFc-Xqzubzz81AtvGrLA@mail.gmail.com>
References: <BANLkTimQ_mqPq0iFc-Xqzubzz81AtvGrLA@mail.gmail.com>
On May 28, 2011, at 7:19 AM, Selva manickaraja wrote:
> Though we know this is due to an application bug, the db should not be repeating it non-stop until halting to an end.
This is a bug in your application. It puts a connection into an error state, doesn't rollback, and keeps submitting transactions and failing.
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, mavles78@gmail.com
Subject: Re: PostgreSQL logs filling up file system due to duplicate key error
In-Reply-To: <5C68D2EA-F5DD-4C5B-A5C2-5A5F1DF4A358@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox