this out.
Best Regards
Dave
From: Day, David
Sent: Wednesday, February 18, 2015 8:07 AM
To: 'Guy Helmer'
Cc: 'pgsql-general@postgresql.org'
Subject: RE: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
Update/Information sharing: ( FreeBSD 10.0 (amd
13th.
Regards
Dave Day
From: Guy Helmer [mailto:ghel...@palisadesystems.com]
Sent: Thursday, February 12, 2015 6:19 PM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
On Feb 12, 2015, at 3:21 PM, Day
: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
On Feb 12, 2015, at 3:21 PM, Day, David
mailto:d...@redcom.com>> wrote:
Update/Information sharing on my pursuit of segmentation faults
FreeBSD 10.0-RELEASE-p12 amd64
Postgres version 9.3.5
Below are three postgres core
> On Feb 12, 2015, at 3:21 PM, Day, David wrote:
>
> Update/Information sharing on my pursuit of segmentation faults
>
> FreeBSD 10.0-RELEASE-p12 amd64
> Postgres version 9.3.5
>
> Below are three postgres core files generated from two different machine (
> Georgia and Alabama ) on Feb 11.
Update/Information sharing on my pursuit of segmentation faults
FreeBSD 10.0-RELEASE-p12 amd64
Postgres version 9.3.5
Below are three postgres core files generated from two different machine (
Georgia and Alabama ) on Feb 11.
These cores would not be caused from an environment update issue th
On Fri, Jan 30, 2015 at 9:54 AM, Day, David wrote:
>
> Alan,
>
>
>
> I tried as you suggested, I believe the gdb debugger is giving some false
> indication about threads.
>
> Whether I attach to a newly launched backend or a backend that has been
> executing the suspect perlu function.
>
> The
segmentation fault
Thanks for your assistance on this matter.
Dave
From: Alex Hunsaker [mailto:bada...@gmail.com]
Sent: Thursday, January 29, 2015 6:10 PM
To: Day, David
Cc: pgsql-general@postgresql.org; Tom Lane
Subject: Re: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
On
On Thu, Jan 29, 2015 at 1:54 PM, Day, David wrote:
> Thanks for the inputs, I’ll attempt to apply it and will update when I
> have some new information.
>
>
>
BTW a quick check would be to attach with gdb right after you connect,
check info threads (there should be none), run the plperlu proced
fault postgres 9.3.5 core dump perlu
related ?
On Thu, Jan 29, 2015 at 8:40 AM, Tom Lane
mailto:t...@sss.pgh.pa.us>> wrote:
"Day, David" mailto:d...@redcom.com>> writes:
> I am amending the info threads info there are two threads.
Well, that's your problem ri
On Thu, Jan 29, 2015 at 8:40 AM, Tom Lane wrote:
> "Day, David" writes:
> > I am amending the info threads info there are two threads.
>
> Well, that's your problem right there. There should never, ever be more
> than one thread in a Postgres backend process: none of the code in the
> backend i
"Day, David" writes:
> I am amending the info threads info there are two threads.
Well, that's your problem right there. There should never, ever be more
than one thread in a Postgres backend process: none of the code in the
backend is meant for a multithreaded situation, and so there are no
int
infrequency of the segmentation fault puzzling.
Regards
Dave
From: Alex Hunsaker [mailto:bada...@gmail.com]
Sent: Thursday, January 29, 2015 12:58 AM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
On Wed
segmentation fault puzzling.
Regards
Dave
From: Alex Hunsaker [mailto:bada...@gmail.com]
Sent: Thursday, January 29, 2015 12:58 AM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
On Wed, Jan 28, 2015 at 1:23
On Wed, Jan 28, 2015 at 1:23 PM, Day, David wrote:
> It has been some time since we have seen this problem.
> See earlier message on this subject/thread for the suspect plperl
> function executing
> at the time of the core.
>
> Someone on our development team suggested it might relate to some
It has been some time since we have seen this problem.
See earlier message on this subject/thread for the suspect plperl function
executing
at the time of the core.
Someone on our development team suggested it might relate to some build
options of perl.
In particular MULTIPLICITY or THREADS
"Day, David" writes:
> It is very likely that the date of the core was 'touched' to make the rebuilt
> Postgres binary with symbols play nice with gdb.
> Apparently, that was not a great idea based on your comments.
Oh, so you rebuilt with debug enabled and then retrospectively tried to
use that
Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Wednesday, December 03, 2014 3:57 PM
To: Day, David
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] segmentation fault postgres 9.3.5 core dump perlu
related ?
"Day, David" writes:
> We are developing on and runnin
"Day, David" writes:
> We are developing on and running Postgres 9.3.5 on FreeBsd 10.0-p12.
> We have been experiencing a intermittent postgres core dump which
> Seems primarily to be associated with the the 2 functions below.
> Given the onset of this problem, we suspect it has something to
We are developing on and running Postgres 9.3.5 on FreeBsd 10.0-p12.
We have been experiencing a intermittent postgres core dump which
Seems primarily to be associated with the the 2 functions below.
The area of interest is based on the content of the postgres log file which
often indicates
19 matches
Mail list logo
