From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Error dumping 9.4: could not parse numeric array |
Date: | 2017-01-03 14:43:28 |
Message-ID: | 21433.1483454608@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= <devrim(at)gunduz(dot)org> writes:
> I'm trying to take backup on my laptop, but getting an error. This is
> PostgreSQL 9.4.10 on Fedora 25, installed using the community RPMS.
> pg_dump -v output is:
> ===============================================================
> pg_dump: reading extensions
> pg_dump: identifying extension members
> pg_dump: reading schemas
> pg_dump: reading user-defined tables
> pg_dump: reading user-defined functions
> pg_dump: could not parse numeric array "2281": too many numbers
> ===============================================================
> Any idea why this is happening, and how can I find a solution?
The only conclusion I can draw is that you have a row in pg_proc
in which proargtypes has more entries than pronargs says there
should be. How it got that way is not apparent --- but you could
start by seeing if you can identify the corrupt row(s).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim Gündüz | 2017-01-03 15:05:43 | Re: Error dumping 9.4: could not parse numeric array |
Previous Message | Adrian Klaver | 2017-01-03 14:18:59 | Re: Error dumping 9.4: could not parse numeric array |