| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Nigel Bishop" <Nigel(dot)Bishop(at)ioko(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Question about Shared memory and PG |
| Date: | 2006-08-04 15:35:27 |
| Message-ID: | 29193.1154705727@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Nigel Bishop" <Nigel(dot)Bishop(at)ioko(dot)com> writes:
> In the PG log file the errors were:
> 2006-08-03 21:49:18 BST FATAL: invalid frontend message type 50
> 2006-08-03 21:49:18 BST LOG: unexpected EOF on client connection
> 2006-08-03 21:49:18 BST LOG: unexpected EOF on client connection
These look to me like your client(s) having a problem, not the server.
Or as you say it could have been a network hiccup.
I think the SHMMAX setting was unrelated, and had your operator not
insisted on waving a dead chicken by rebooting the database, you'd
still not know that someone had changed SHMMAX ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rodolfo Borges | 2006-08-04 15:57:22 | installing on user account |
| Previous Message | Tom Lane | 2006-08-04 15:00:28 | Re: Background writer memory bloat? |