Re: Duplicate rows during pg_dump

From: Marc Mamin <M(dot)Mamin(at)intershop(dot)de>
To: "'Jim Nasby'" <Jim(dot)Nasby(at)BlueTreble(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Chaz Yoon <chaz(at)shopspring(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Duplicate rows during pg_dump
Date: 2015-10-26 07:49:49
Message-ID: B6F6FD62F2624C4C9916AC0175D56D884209D8DC@jenmbs01.ad.intershop.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> -----Original Message-----
> From: Jim Nasby [mailto:Jim(dot)Nasby(at)BlueTreble(dot)com]
> Sent: Montag, 26. Oktober 2015 01:55
> To: Marc Mamin; Adrian Klaver; Chaz Yoon; pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Duplicate rows during pg_dump
>
> On 10/24/15 3:15 PM, Marc Mamin wrote:
> >>> Any suggestions for what to look for next? Is it table corruption?
> > Most likely is the index corrupt, not the table.
> > You should check for further duplicates, fix them and as Adrian
> > writes, build a new index an then drop the corrupt one.
> >
> > I've seen this a few times before, and if I recall well it was always
> after some plate got full.
> > Is AWS getting out of space:)
>
> You should report this to the RDS team, because an out of space
> condition shouldn't leave multiple values in the index. I suspect
> they've made a modification somewhere that is causing this. It could be
> a base Postgres bug, but I'd think we'd have caught such a bug by
> now...

Last time I got this trouble was 4-5 years ago...

regards,

Marc Mamin

> --
> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in
> Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in
> Treble! http://BlueTreble.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rafal Pietrak 2015-10-26 07:54:52 Re: partial JOIN (was: ID column naming convention)
Previous Message David Blomstrom 2015-10-26 05:19:28 Re: Recursive Arrays 101