From: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
---|---|
To: | "'Chaya Gilburt'" <chaya(at)nybc(dot)com(dot)br> |
Cc: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Odd Behavior After Multiple Deletes |
Date: | 2013-05-24 02:49:39 |
Message-ID: | 004501ce5829$568ba9a0$03a2fce0$@kapila@huawei.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bakyaraj K | 2013-05-24 08:40:57 | Error |
Previous Message | Heikki Linnakangas | 2013-05-23 11:56:35 | Re: BUG #8173: Inserting heap tuples in bulk in COPY patch return wrong line on failure 999 out of 1000 times. |