From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Victor Hugo dos Santos <listas(dot)vhs(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: ERROR: invalid memory alloc request size 4294967293 |
Date: | 2011-01-04 22:02:41 |
Message-ID: | 16074.1294178561@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Victor Hugo dos Santos <listas(dot)vhs(at)gmail(dot)com> writes:
> On Tue, Jan 4, 2011 at 1:05 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> It looks like a corrupted-data problem from here. You need to isolate
>> and delete the bad row(s).
> # su - postgres -c "psql bacula -c 'SELECT md5 from public.file OFFSET
> 1417610 LIMIT 1'"
> server closed the connection unexpectedly
So you've got some rows that are corrupted badly enough to crash the
backend :-(.
> In others words.. if I run the same command two times, I get a error,
> and if I rerun the same command, work !!!
When you're running long seqscans like these, you need to turn off
"synchronize_seqscans" to get reproducible results. With that flag
turned on, scans may start from somewhere in the middle of the table
instead of always starting from the beginning.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | ojas dubey | 2011-01-05 06:00:08 | Re: Find all running postgres DB servers on a network |
Previous Message | Victor Hugo dos Santos | 2011-01-04 19:57:24 | Re: ERROR: invalid memory alloc request size 4294967293 |