| Lists: | pgsql-bugs |
|---|
| From: | weixing(dot)sun(at)gmail(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #6696: 9.2beta2 crashed when having shared_buffers>20GB |
| Date: | 2012-06-16 17:39:29 |
| Message-ID: | E1Sfwy9-0000L9-Af@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 6696
Logged by: weixing
Email address: weixing(dot)sun(at)gmail(dot)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
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | weixing(dot)sun(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6696: 9.2beta2 crashed when having shared_buffers>20GB |
| Date: | 2012-06-18 15:58:49 |
| Message-ID: | 10978.1340035129@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
weixing(dot)sun(at)gmail(dot)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