Re: BUG #16043: Duplicate Entry Key Message on postgres

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Komal Sookee <komal(dot)sookee(at)spoonconsulting(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Irfaan Coonjbeeharry <irfaan(dot)coonjbeeharry(at)spoonconsulting(dot)com>
Subject: Re: BUG #16043: Duplicate Entry Key Message on postgres
Date: 2019-10-07 19:58:36
Message-ID: 20191007195836.6o43lheffo3fxnu5@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Oct 07, 2019 at 05:40:14PM +0400, Komal Sookee wrote:
>Hello Tom,
>
>Could you help me out to find out a solution?
>
>What information do you need?
>

I'd start by reading the wiki page Tom already pointed you to. That's a
pretty extensive summary and it should give you at least some rought
idea what information would be useful ...

In this particular case, you should probably start with an explanation
what environment you're using, what queries are generated by the
DataSet, what exactly "Duplicate Entry Key" means in the context of the
application, and scavenge all the various logs (application, database,
...) for as much additional details as possible.

Considering PostgreSQL does not generate any "Duplicate Entry Key"
errors (there are no such messages in the source code), this very much
seems like an issue in the application and not in the database. So maybe
the first thing you need to do is convincing us this actually is a
database issue.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Vondra 2019-10-07 20:53:41 Re: BUG #16031: Group by returns duplicate groups
Previous Message Andrew Gierth 2019-10-07 18:29:11 Re: BUG #16031: Group by returns duplicate groups