PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID16043
PG Version11.0
OSCentos 7
Opened2019-10-07 11:21:45+00
Reported byJason John
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      16043
Logged by:          Jason John
Email address:      (redacted)
PostgreSQL version: 11.0
Operating system:   Centos 7
Description:        

We are currently experiencing a problem with DataSet objects that behave
differently between Oracle and Postgres.

When we perform "Next Page" / "Previous Page" repeatedly the application
crashes with a "Duplicate Entry Key" Message on postgres.

At the following address
http://docwiki.embarcadero.com/RADStudio/Rio/en/Browsing_Tables_(FireDAC)
(See: Avoiding "Unique Key Violation" Error in LDW Mode at the end of the
page), it seems that our difficulties can come from character encoding
problem. Is there any solution?

Messages

DateAuthorSubject
2019-10-07 11:21:45+00PG Bug reporting formBUG #16043: Duplicate Entry Key Message on postgres
2019-10-07 13:35:55+00Tom LaneRe: BUG #16043: Duplicate Entry Key Message on postgres
2019-10-07 13:40:14+00Komal SookeeRe: BUG #16043: Duplicate Entry Key Message on postgres
2019-10-07 19:58:36+00Tomas VondraRe: BUG #16043: Duplicate Entry Key Message on postgres