On 1/06/2011 1:28 AM, Rikard Pavelic wrote:
The following bug has been logged online:
Bug reference: 6046
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 9.1 beta 1
Operating system: Windows 7 64bit
Description: select current_date crashes postgres
Details:
select current_time
or select current_date
results in postgres crash.
The crash is a segfault:
2011-06-01 08:29:04 WST LOG: server process (PID 2420) was terminated
by exception 0xC0000005
I've got a crash dump and am looking into it now. In the mean time,
what's even more worrying is this:
2011-06-01 08:33:18 WST WARNING: terminating connection because of crash of
another server process
2011-06-01 08:33:18 WST 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.
2011-06-01 08:33:18 WST HINT: In a moment you should be able to reconnect to
the database and repeat your command.
2011-06-01 08:33:18 WST LOG: all server processes terminated; reinitializing
2011-06-01 08:33:28 WST FATAL: pre-existing shared memory block is still in use
2011-06-01 08:33:28 WST HINT: Check if there are any old server processes
still running, and terminate them.
It looks like Pg isn't coming back up after the backend crash. There
are no postgres.exe processes hanging around, and I can start PostgreSQL
back up from services.msc without a problem, but it doesn't successfully
re-launch its _self_ after a crash.
--
Craig Ringer
Tech-related writing at http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
