From: Pablo Alcaraz <pabloa@laotraesquina.com.ar>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: corrupted shared memory message
Date: Sun, 20 Apr 2008 16:53:21 -0300
Message-ID: <480B9F31.8070301@laotraesquina.com.ar> (raw)
Hi All!
We have a database running smoothly for months. 2 days ago I get this
error message. I tried a restore, a full restore (deleting the old
database and recovering from backup all the information) but we are
getting this error every time.
In this case I got this error when I was trying to recover the database
from a backup. Sometimes I can recover it and restart the application,
but after a while I get the same error message again and again.
Any ideas what's going on? I checked filesystem and it is ok.
Regards
Pablo
2008-04-20 12:01:13 EDT [5309] [2758789251] [480b68c9.14bd-1] ERROR:
date/time field value out of range: "2008-01-275:51:08.631"
2008-04-20 12:01:13 EDT [5309] [2758789251] [480b68c9.14bd-2] HINT:
Perhaps you need a different "datestyle" setting.
2008-04-20 12:01:13 EDT [5309] [2758789251] [480b68c9.14bd-3] CONTEXT:
COPY venta_00015, line 11626137, column dmodi: "2008-01-275:51:08.631"
2008-04-20 12:01:13 EDT [5309] [2758789251] [480b68c9.14bd-4]
STATEMENT: COPY venta_00015 (idventa, idventapadre, estado, dmodi,
puntuacion, moviseria
lizados) FROM stdin;
2008-04-20 12:01:13 EDT [5309] [2758789324] [480b68c9.14bd-5] ERROR:
invalid input syntax for integer: "15820584,"
2008-04-20 12:01:13 EDT [5309] [2758789324] [480b68c9.14bd-6] CONTEXT:
COPY venta_00018, line 8388339, column idventapadre: "15820584,"
2008-04-20 12:01:13 EDT [5309] [2758789324] [480b68c9.14bd-7]
STATEMENT: COPY venta_00018 (idventa, idventapadre, estado, dmodi,
evaluacion, moviseria
lizados) FROM stdin;
[5995] [] [-1] PANIC: corrupted item pointer: offset = 7152, size = 8208
[5148] [] [-1] LOG: autovacuum process (PID 5995) was terminated by
signal 6
[5148] [] [-2] LOG: terminating any other active server processes
2008-04-20 11:50:36 EDT [5166] [0] [480b664c.142e-1] WARNING:
terminating connection because of crash of another server process
2008-04-20 11:50:36 EDT [5166] [0] [480b664c.142e-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit,
because another server process exited abnormally and possibly corrupted
shared memory.
2008-04-20 11:50:36 EDT [5166] [0] [480b664c.142e-3] HINT: In a moment
you should be able to reconnect to the database and repeat your command.
2008-04-20 12:02:35 EDT [5328] [0] [480b691b.14d0-1] WARNING:
terminating connection because of crash of another server process
2008-04-20 12:02:35 EDT [5328] [0] [480b691b.14d0-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit,
because another server process exited abnormally and possibly corrupted
shared memory.
2008-04-20 12:02:35 EDT [5328] [0] [480b691b.14d0-3] HINT: In a moment
you should be able to reconnect to the database and repeat your command.
2008-04-20 11:58:49 EDT [5269] [0] [480b6839.1495-1] WARNING:
terminating connection because of crash of another server process
2008-04-20 11:58:49 EDT [5269] [0] [480b6839.1495-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit,
because another server process exited abnormally and possibly corrupted
shared memory.
2008-04-20 11:58:49 EDT [5269] [0] [480b6839.1495-3] HINT: In a moment
you should be able to reconnect to the database and repeat your command.
2008-04-20 12:01:13 EDT [5309] [2758789363] [480b68c9.14bd-8] WARNING:
terminating connection because of crash of another server process
/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pabloa@laotraesquina.com.ar
Subject: Re: corrupted shared memory message
In-Reply-To: <480B9F31.8070301@laotraesquina.com.ar>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox