Known issues in Greenplum Database related to Greenplum Database Replication(Segment Mirroring, Resync, Transaction Management)

posted Jan 25, 2014, 9:06 AM by Sachchida Ojha

1. Issue 21917

In some rare cases after the Greenplum Database utility gprecoverseg was run, some append-optimized tables and a persistent table were detected having less data on a mirror segment corresponding to a primary segment.

2. Issue 19788

In some rare circumstances, performing a full recovery with gprecoverseg

fails due to inconsistent LSN.

Workaround: Stop and restart the database. Then perform a full recovery with

gprecoverseg.

Comments