Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1
От | Bruce Momjian |
---|---|
Тема | Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1 |
Дата | |
Msg-id | 20131010164712.GA7078@momjian.us обсуждение исходный текст |
Ответ на | 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>) |
Ответы |
Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row
number 0 is out of range 0..-1
|
Список | pgsql-general |
On Sat, Sep 14, 2013 at 09:40:01PM -0400, Robert Nix wrote: > Running a pg_upgrade task is causing Segmentation fault: > > command: "/usr/lib/postgresql/9.3/bin/pg_dump" --host "/var/lib/postgresql" > --port 50432 --username "postgres" --schema-only --quote-all-identifiers > --binary-upgrade --format=custom --file="pg_upgrade_dump_6064585.custom" "u" > >> "pg_upgrade_dump_6064585.log" 2>&1 > pg_dump: row number 0 is out of range 0..-1 > Segmentation fault (core dumped) This error is coming from libpq, specifically check_tuple_field_number(), which is called by PQgetvalue(), PQgetlength(), and PQgetisnull(). As I have never seen this error before, there might be something wrong with the system catalogs on that cluster. It would be good to run pg_dump --binary-upgrade on that database and try to identify the object being dumped that is causing the crash. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. +
В списке pgsql-general по дате отправления: