Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Robert Nix <robert(at)urban4m(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1
Date: 2013-09-16 16:32:18
Message-ID: CAMkU=1wzOoMuRwyZ7PKPoP1crnURY=u-tJjgfXt8AWoAe_d1iQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Sep 15, 2013 at 8:02 PM, Robert Nix <robert(at)urban4m(dot)com> wrote:

> If you do the dump using 9.1's pg_dump without --binary-upgrade, and then
>> load that dump file into a new empty 9.1 server, then does it crash if you
>> take a dump against *that* server?
>>
>
> I'll give it a try.
>
> If so, would you be allowed to post that dump file?
>>
>
> I will not be able to provide the dump file but i will try to isolate the
> contents causing the issue and hopefully be able to provide a minimal dump
> file that doesn't contain any proprietary data yet still reproduces the
> crash. It's a fair amount of data, 45+G, so if i can reproduce it in a new
> database, isolating it may take some time.
>

The dump should just have the schema, not the data, because of
--schema-only.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message NWRFC Portland 2013-09-16 20:40:15 Re: Postgres 9.2.4 "Double Precision" Precision
Previous Message Vincent Veyron 2013-09-16 15:48:03 Re: [PG9.1] CTE usage