BUG #4112: Error on access table's data

From: "Malcus" <malcus(at)terra(dot)com(dot)br>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4112: Error on access table's data
Date: 2008-04-17 18:17:25
Message-ID: 200804171817.m3HIHPwS073403@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 4112
Logged by: Malcus
Email address: malcus(at)terra(dot)com(dot)br
PostgreSQL version: 8.2.7
Operating system: Windows 2003 Server
Description: Error on access table's data
Details:

When I execute a SELECT command in a table like "SELECT field1, field2 FROM
table" the database shutdown by "him self".

On pg_log directory I found this LOG [1].

Then I execute a TRUNCATE command in this table and do the same SELECT no
error occur, but of course, no data was get.

[1]:
2008-04-17 14:57:33 :LOG: server process (PID 4084) exited with exit code
-1073741819
2008-04-17 14:57:33 :LOG: terminating any other active server processes
2008-04-17 14:57:33 db1 127.0.0.1 :WARNING: terminating connection because
of crash of another server process
2008-04-17 14:57:33 db1 127.0.0.1 :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-17 14:57:33 db1 127.0.0.1 :HINT: In a moment you should be able to
reconnect to the database and repeat your command.
2008-04-17 14:57:33 postgres 127.0.0.1 :WARNING: terminating connection
because of crash of another server process
2008-04-17 14:57:33 postgres 127.0.0.1 :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-17 14:57:33 postgres 127.0.0.1 :HINT: In a moment you should be
able to reconnect to the database and repeat your command.
2008-04-17 14:57:33 :LOG: all server processes terminated;
reinitializing
2008-04-17 14:57:33 :LOG: database system was interrupted at 2008-04-17
14:56:10 Hora oficial do Brasil
2008-04-17 14:57:33 :LOG: checkpoint record is at 2A/36FFB2E8
2008-04-17 14:57:33 :LOG: redo record is at 2A/36FFB2E8; undo record is
at 0/0; shutdown FALSE
2008-04-17 14:57:33 :LOG: next transaction ID: 0/2266271; next OID:
13896010
2008-04-17 14:57:33 :LOG: next MultiXactId: 1; next MultiXactOffset: 0
2008-04-17 14:57:33 :LOG: database system was not properly shut down;
automatic recovery in progress
2008-04-17 14:57:33 :LOG: redo starts at 2A/36FFB338
2008-04-17 14:57:34 :LOG: record with zero length at 2A/3705EC40
2008-04-17 14:57:34 :LOG: redo done at 2A/3705EBF8
2008-04-17 14:57:35 :LOG: database system is ready
2008-04-17 14:58:37 :LOG: server process (PID 1968) exited with exit code
-1073741819
2008-04-17 14:58:37 :LOG: terminating any other active server processes

Browse pgsql-bugs by date

  From Date Subject
Next Message Adhikari, Tika Ram 2008-04-18 15:34:37 Request
Previous Message Alvaro Herrera 2008-04-17 14:12:24 Re: Server does not start when log_statement_stats is set to on