So will that be an 8.3.13?
Sam
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, 10 December 2010 3:32 PM
To: Samuel Stearns
Cc: Shoaib Mir; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Postgres Crash
Samuel Stearns writes:
> I'm getting info from our sysa
Samuel Stearns writes:
> I'm getting info from our sysadmins that we can't re-compile because we don't
> have the sun compiler. Is this fixed in a later release of postgres?
The fix will be in next week's releases.
regards, tom lane
--
Sent via pgsql-admin mailing lis
Tom,
I'm getting info from our sysadmins that we can't re-compile because we don't
have the sun compiler. Is this fixed in a later release of postgres?
Sam
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, 10 December 2010 3:22 PM
To: Samuel Stearns
Cc: Shoai
Tom,
So you are in agreement that the fix is:
This simple patch seem to fix the problem
--- src/backend/postmaster/postmaster.c.orig2010-10-27
19:07:42.0 +0400
+++ src/backend/postmaster/postmaster.c 2010-10-27 19:08:25.0 +0400
@@ -1917,7 +1917,7 @@
if (port->
Samuel Stearns writes:
> Yes, with gssapi.
Well, then we have our smoking gun, but it's still not clear *why*
the setsockopt() call failed.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://w
Tom,
Yes, with gssapi.
Sam
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, 10 December 2010 3:02 PM
To: Samuel Stearns
Cc: Shoaib Mir; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Postgres Crash
Samuel Stearns writes:
> Its not our build - its the one d
Samuel Stearns writes:
> Its not our build - its the one downloaded some the postgres homepage
> from http://www.postgresql.org/ftp/binary/v8.3.12/solaris/solaris10/i386/
pg_config --configure would tell you how it was built.
regards, tom lane
--
Sent via pgsql-admin ma
Its not our build - its the one downloaded some the postgres homepage
from http://www.postgresql.org/ftp/binary/v8.3.12/solaris/solaris10/i386/
Sam
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, 10 December 2010 2:53 PM
To: Samuel Stearns
Cc: Shoaib Mir; pgsq
Samuel Stearns writes:
> Could it possibly be this?:
> http://postgresql.1045698.n5.nabble.com/BUG-5731-postmaster-sometimes-dumps-core-when-handling-local-connections-td3239029.html
Yeah, I'd just been off digging through the code to arrive at that same
theory. Did you build with GSSAPI suppor
Samuel Stearns writes:
> [r...@udrv] # pstack /root/core
> core '/root/core' of 771: /opt/postgres/8.3-community/bin/postmaster -F
> 081a8562 ConnCreate (5) + b6
> 081a791b ServerLoop (8047e68, 83b7930, 2, fead58be, 8047e68, 83c28b8) + db
> 081a73f1 PostmasterMain (2, 83b7930) + ab5
>
Tom,
Could it possibly be this?:
http://postgresql.1045698.n5.nabble.com/BUG-5731-postmaster-sometimes-dumps-core-when-handling-local-connections-td3239029.html
Sam
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, 10 December 2010 2:17 PM
To: Samuel Stearns
C
Thanks Tom,
We don't have gdb. We have mdb and pstack. From the core:
[r...@udrv] # mdb /opt/postgres/8.3-community/bin/postmaster /root/core
Loading modules: [ libc.so.1 ld.so.1 ]
> ::status
debugging core file of postmaster (32-bit) from udrv
file: /opt/postgres/8.3-community/bin/postmaster
Samuel Stearns writes:
> Tom, no useful messages in the log prior. I do have a 47M core dump. What
> should I do with that?
If you use gdb, try
$ gdb /path/to/postmaster /path/to/corefile
gdb> bt
... useful info here ...
gdb> quit
I think the preferred debugge
Yes.
From: pgsql-admin-ow...@postgresql.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Shoaib Mir
Sent: Friday, 10 December 2010 2:06 PM
To: Samuel Stearns
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Postgres Crash
On Fri, Dec 10, 2010 at 2:33 PM, Samuel Stearns
mailto:sstea
On Fri, Dec 10, 2010 at 2:33 PM, Samuel Stearns
wrote:
> Thanks Tom and Shoaib,
>
>
>
> Shoaib, I did not delete postmaster.pid. I killed the children and
> re-started successfully.
>
>
>
So is the database server all good and working fine now??
--
Shoaib Mir
http://shoaibmir.wordpress.com/
Thanks Tom and Shoaib,
Shoaib, I did not delete postmaster.pid. I killed the children and re-started
successfully.
Tom, no useful messages in the log prior. I do have a 47M core dump. What
should I do with that?
Sam
From: Shoaib Mir [mailto:shoaib...@gmail.com]
Sent: Friday, 10 December 20
On Fri, Dec 10, 2010 at 2:17 PM, Samuel Stearns
wrote:
> Howdy,
>
>
>
> Environment:
>
>
>
> Solaris 10
>
> Postgres 8.3.12
>
>
>
> Postgres crashed and left 26 postmaster processes active in it’s wake.
> Killed the children and re-started postgres successfully. Messages from the
> log:
>
>
>
> D
Samuel Stearns writes:
> Environment:
> Solaris 10
> Postgres 8.3.12
> Postgres crashed and left 26 postmaster processes active in it's wake.
> Killed the children and re-started postgres successfully. Messages from the
> log:
> Dec 10 11:52:15 udrv postgres[771]: [ID 748848 local0.info] [6
Howdy,
Environment:
Solaris 10
Postgres 8.3.12
Postgres crashed and left 26 postmaster processes active in it's wake. Killed
the children and re-started postgres successfully. Messages from the log:
Dec 10 11:52:15 udrv postgres[771]: [ID 748848 local0.info] [6-1]
host=,user=,db= LOG: sets
19 matches
Mail list logo
