From: | Sam Nelson <samn(at)consistentstate(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Memory Errors |
Date: | 2010-09-08 18:56:51 |
Message-ID: | AANLkTi=9c9V5Qg09PXBZ-vz9=kGrzs2noUfCt==pYG8H@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hey, a client of ours has been having some data corruption in their
database. We got the data corruption fixed and we believe we've discovered
the cause (they had a script killing any waiting queries if the locks on
their database hit 1000), but they're still getting errors from one table:
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: invalid memory alloc request
size 18446744073709551613
pg_dump: The command was: COPY public.foo (<columns>) TO stdout;
That seems like an incredibly large memory allocation request - it shouldn't
be possible for the table to really be that large, should it? Any idea what
may be wrong if it's actually trying to allocate that much memory for a copy
command?
From | Date | Subject | |
---|---|---|---|
Next Message | Darren Duncan | 2010-09-08 18:57:28 | Re: how do i count() similar items |
Previous Message | Donald Catanzaro, PhD | 2010-09-08 18:48:25 | Re: Copy From csv file with double quotes as null |