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

From Jeff Janes
Subject Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1
Date
Msg-id CAMkU=1zL=UhVOt39Mo8XecKkHmXe=8BdH7rtx30njzJDfgk2Qg@mail.gmail.com
Whole thread Raw
In response to Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1  (Robert Nix <robert@urban4m.com>)
Responses Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1  (Robert Nix <robert@urban4m.com>)
List pgsql-general
On Sun, Sep 15, 2013 at 5:06 PM, Robert Nix <robert@urban4m.com> wrote:

What happens if you manually run the pg_dump command quoted above against a running 9.1 server, outside of the context of pg_upgrade?  (Your port will be probably be different from 50432)

If that still crashes, What if you drop the --binary-upgrade option?  The --format=custom option?
 
I started the 9.1 server normally and ran the above pg_dump (with the appropriate port for that instance).

| w/ -binary-upgrade | w/ --format=custom | crashed? |
|        yes         |         no         |   yes    |
|         no         |        yes         |    no    |
|        yes         |        yes         |   yes    |

So it seem the -binary-upgrade option has caused some problem. And the same crash happens regardless of whether i use the 9.1's or 9.3's pg_dump.


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?  If so, would you be allowed to post that dump file?
 
Cheers,

Jeff

pgsql-general by date:

Previous
From: Chris Curvey
Date:
Subject: Re: help getting a backtrace from 9.2 on Ubuntu 13.04?
Next
From: Robert Nix
Date:
Subject: Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1