Re: Odd Behavior After Multiple Deletes - Mailing list pgsql-bugs

From Amit Kapila
Subject Re: Odd Behavior After Multiple Deletes
Date
Msg-id 004501ce5829$568ba9a0$03a2fce0$@kapila@huawei.com
Whole thread Raw
In response to Odd Behavior After Multiple Deletes  ("Chaya Gilburt" <chaya@nybc.com.br>)
List pgsql-bugs
On Friday, May 24, 2013 6:04 AM Chaya Gilburt wrote:
> Dear Amit Kapila,
>
> The apparent problem with duplicate rows appearing in the database was
> solved. I forgot that I had modified a program to insert payments
> directly
> to the database. Not only that, but I also did not have the program
> delete
> the batch files used, only reopen them as an append. Every time the
> batch
> job was reused, the older inserts still inside the batch file were
> re-inserted along with the new inserts.  I am sorry to have wasted your
> time, but glad that the problem was due to my own idiocy and not
> Postgresql,
> as we love using it.

It is great that you have found the problem in your application and
continuing to use PostgreSql.
I have kept in cc to postgresql mailing chain, as I think it should be known
to every one, so that
any body faces similar problem in future can refer this mail chain.


With Regards,
Amit Kapila.

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #8173: Inserting heap tuples in bulk in COPY patch return wrong line on failure 999 out of 1000 times.
Next
From: Bakyaraj K
Date:
Subject: Error