BUG #6696: 9.2beta2 crashed when having shared_buffers>20GB
The following bug has been logged on the website:
Bug reference: 6696
Logged by: weixing
Email address: weixing.sun@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: RHEL6.1
Description:
Hi,
I know this NON-GA version issue could not be placed here, but please let me
know if you have any entries.
Currently , I met a tricky bug of Postgres 9.2beta2 when having > 20GB
buffer pool:
###################################
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.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server process
################################
Above err msg will fill out my stderr log file, and refuse all the requests
from the middle-tier of running my workload.
Any comments?
Thanks a lot!
Weixing
weixing.sun@gmail.com writes:
Currently , I met a tricky bug of Postgres 9.2beta2 when having > 20GB
buffer pool:
It seems fairly unlikely that having shared_buffers that high is alone
sufficient to cause a crash, if indeed it's even related to the problem.
What were you doing exactly? We need full instructions to reproduce the
failure.
regards, tom lane