As a further update on this, we dropped the offending PKs, removed the
duplicated rows using delete from where ctid in (select
max(ctid) from group by having count(*) > 1), and then
rebuilt the primary key. Thus far, we've seen no further corruption. We
were wondering if it was a restore corru
Copying the list this time.
On Tue, Aug 28, 2018 at 7:54 AM Daniel J Peacock
wrote:
>
>
> On Mon, Aug 27, 2018 at 7:14 PM David Rowley
> wrote:
>
>> On 28 August 2018 at 07:50, Daniel J Peacock
>> wrote:
>> > I've got an odd situation with a table that has a varchar(255) as the
>> > primary ke
On 28 August 2018 at 07:50, Daniel J Peacock wrote:
> I've got an odd situation with a table that has a varchar(255) as the
> primary key that is getting key values from an Elasticsearch engine. What
> I'm finding is that even though there is a primary key on the table, I am
> getting duplicated
> On Aug 27, 2018, at 1:50 PM, Daniel J Peacock wrote:
>
> Good afternoon, all.
> I've got an odd situation with a table that has a varchar(255) as the primary
> key that is getting key values from an Elasticsearch engine. What I'm
> finding is that even though there is a primary key on the
Good afternoon, all.
I've got an odd situation with a table that has a varchar(255) as the
primary key that is getting key values from an Elasticsearch engine. What
I'm finding is that even though there is a primary key on the table, I am
getting duplicated keys in the data and the constraint is n
