Re: ERROR: invalid memory alloc request size 4294967293 - Mailing list pgsql-admin

On Tue, Jan 4, 2011 at 1:05 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Victor Hugo dos Santos <listas.vhs@gmail.com> writes:
>> any idea ???
>
> It looks like a corrupted-data problem from here.  You need to isolate
> and delete the bad row(s).

Hello again...

this is very, very strange !! :D
(sorry for long message, but I'm trying to sent all information)


I was trying of isolate the "bad rows" in base a this article
http://archives.postgresql.org/pgsql-admin/2003-06/msg00204.php

first I create a function run a select the column "md5" (md5 and lstat
are both with errors) row-to-row..
after a time, I discoverer that the (first) row with problem is the "1417610"

So, now I run the command manually:

=========================
# su - postgres -c "psql bacula -c 'SELECT md5 from public.file OFFSET
1417610 LIMIT 1'"
             md5
-----------------------------
 WPC7vlHBLbGDA5XL6bsuBVsVVEM
(1 row)


# su - postgres -c "psql bacula -c 'SELECT md5 from public.file OFFSET
1417610 LIMIT 1'"
server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.
connection to server was lost


# su - postgres -c "psql bacula -c 'SELECT md5 from public.file OFFSET
1417610 LIMIT 1'"
             md5
-----------------------------
 WPC7vlHBLbGDA5XL6bsuBVsVVEM
(1 row)

# su - postgres -c "psql bacula -c 'SELECT md5 from public.file OFFSET
1417610 LIMIT 1'"
server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.
connection to server was lost
====================

In others words.. if I run the same command two times, I get a error,
and if I rerun the same command, work !!!
In the logs of postgresql I found after:


=========================
2011-01-04 16:40:35 CLST STATEMENT:  SELECT md5 from public.file
OFFSET 800000 LIMIT 1
2011-01-04 16:40:36 CLST DEBUG:  reaping dead processes
2011-01-04 16:40:36 CLST DEBUG:  server process (PID 15542) was
terminated by signal 11: Segmentation fault
2011-01-04 16:40:36 CLST LOG:  server process (PID 15542) was
terminated by signal 11: Segmentation fault
2011-01-04 16:40:36 CLST LOG:  terminating any other active server processes
2011-01-04 16:40:36 CLST DEBUG:  sending SIGQUIT to process 15533
2011-01-04 16:40:36 CLST DEBUG:  sending SIGQUIT to process 15534
2011-01-04 16:40:36 CLST DEBUG:  sending SIGQUIT to process 15535
2011-01-04 16:40:36 CLST DEBUG:  sending SIGQUIT to process 15536
2011-01-04 16:40:36 CLST DEBUG:  shmem_exit(-1): 0 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  proc_exit(-1): 0 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  shmem_exit(-1): 0 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  proc_exit(-1): 0 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  shmem_exit(-1): 0 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  proc_exit(-1): 0 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  shmem_exit(-1): 0 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  proc_exit(-1): 0 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  reaping dead processes
2011-01-04 16:40:36 CLST LOG:  all server processes terminated; reinitializing
2011-01-04 16:40:36 CLST DEBUG:  shmem_exit(1): 3 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  invoking IpcMemoryCreate(size=32595968)
2011-01-04 16:40:36 CLST LOG:  database system was interrupted; last
known up at 2011-01-04 16:40:28 CLST
2011-01-04 16:40:36 CLST DEBUG:  checkpoint record is at 6/83C484E4
2011-01-04 16:40:36 CLST DEBUG:  redo record is at 6/83C484E4; shutdown TRUE
2011-01-04 16:40:36 CLST DEBUG:  next transaction ID: 0/416024; next OID: 156073
2011-01-04 16:40:36 CLST DEBUG:  next MultiXactId: 1; next MultiXactOffset: 0
2011-01-04 16:40:36 CLST LOG:  database system was not properly shut
down; automatic recovery in progress
2011-01-04 16:40:36 CLST LOG:  record with zero length at 6/83C48528
2011-01-04 16:40:36 CLST LOG:  redo is not required
2011-01-04 16:40:36 CLST DEBUG:  transaction ID wrap limit is
2147484295, limited by database "template1"
2011-01-04 16:40:36 CLST DEBUG:  shmem_exit(0): 3 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  proc_exit(0): 2 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  exit(0)
2011-01-04 16:40:36 CLST DEBUG:  shmem_exit(-1): 0 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  proc_exit(-1): 0 callbacks to make
2011-01-04 16:40:36 CLST DEBUG:  reaping dead processes
2011-01-04 16:40:36 CLST LOG:  database system is ready to accept connections
2011-01-04 16:40:36 CLST LOG:  autovacuum launcher started
=========================

maybe the problem is in "6/83C48528" but none idea how fix it.

thanks.

--
--
Victor Hugo dos Santos
Linux Counter #224399