Chris Curvey writes:
>> Hmm, that's pretty interesting. Possibly it's just another
>> manifestation of something scribbling past the end of its allocated
>> chunk, but my credence for that theory is way down if there's no add-on
>> code involved. Does the postmaster log show any messages like
>>
>
>
> Hmm, that's pretty interesting. Possibly it's just another
> manifestation of something scribbling past the end of its allocated
> chunk, but my credence for that theory is way down if there's no add-on
> code involved. Does the postmaster log show any messages like
>WARNING: detect
Chris Curvey writes:
> in reverse order: no third-party, no contrib, no home-brew C.here is a
> stack trace from a fresh build of 9.1 beta 1 built with enable-cassert.
> Program received signal SIGSEGV, Segmentation fault.
> 0x00744777 in AllocSetAlloc (context=0x13f6d08, size=16) a
>
>
> It occurred to me that a simple explanation for a core dump there would
> be if something had scribbled past the end of the preceding palloc
> chunk. That would tend to clobber the "context" link of the palloc
> chunk after it, which would send GetMemoryChunkSpace off into
> never-never land
Chris Curvey writes:
> and, FWIW, here's another trace, which is NEARLY the same as the first one I
> posted, with the difference being a slightly different line number at #3. I
> will be quiet now and leave the brain trust to ponder. Let me know if there
> is anything else I can get for you guy
>
>
>>
and, FWIW, here's another trace, which is NEARLY the same as the first one I
posted, with the difference being a slightly different line number at #3. I
will be quiet now and leave the brain trust to ponder. Let me know if there
is anything else I can get for you guys.
#0 0x006ce
On Thu, Apr 7, 2011 at 10:45 AM, Tom Lane wrote:
> Chris Curvey writes:
> > And voila! Here is the backtrace:
>
> > #0 0x006ce317 in GetMemoryChunkSpace (pointer=0x347cc70) at
> > mcxt.c:264
> > #1 0x006d3d56 in writetup_index (state=0x26fc530, tapenum= > optimized out>, stup=
Chris Curvey writes:
> And voila! Here is the backtrace:
> #0 0x006ce317 in GetMemoryChunkSpace (pointer=0x347cc70) at
> mcxt.c:264
> #1 0x006d3d56 in writetup_index (state=0x26fc530, tapenum= optimized out>, stup=) at tuplesort.c:2924
> #2 0x006d2af7 in dumptuples (st
On 04/07/2011 08:49 PM, Chris Curvey wrote:
Let me see if I can load it somewhere else. And since the only other
machine I have to try it on is a Windows box, I will be able to answer
my own question of "are pg_dump dumps OS-portable?"
The answer there is "mostly". Contrib modules can cause
>
>
> Are you able to distribute your dataset - if not to the general public,
> then to someone interested in identifying the fault?
>
probably not. but let me ask...maybe I can come up with a creative
solution.
> Does the same dataset crash Pg when restored on another machine?
That is a good
On 04/07/2011 06:37 PM, Chris Curvey wrote:
2) install bison, flex and libreadline5-dev (sudo apt-get install
PACKAGE). I already had the gcc package installed
The easy way to do this on Debian/ubuntu, if you're building something
that packages exist for, is (eg):
sudo apt-get build-dep po
>
>
> Nor I. https://launchpad.net/~pitti/+archive/postgresql/+packages doesn't
> seem to list any.
>
> Martin: Are your packages stripped, or do they include minimal debug info
> in the main packages? Do you put your debuginfo debs anywhere accessible?
>
>
I decided to just try building it myself
On 7/04/2011 4:02 AM, Chris Curvey wrote:
Hmmm. I'm on Ubuntu, and running 9.0.3, so I'm getting my packages from
Martin Pitt, per the instructions at
http://www.dctrwatson.com/2010/09/installing-postgresql-9-0-on-ubuntu-10-04/.
I don't seem to see any debug packages there.
Nor I. https://l
On Mon, Apr 4, 2011 at 11:59 PM, Craig Ringer
wrote:
> On 05/04/11 11:18, Chris Curvey wrote:
>
> > This is on Ubuntu 10.10 server, 64-bit on Intel. I'm running Postgres
> > 9.0.3, 64-bit from the ppa repository.
> >
> > What can I do to help the developers find the root cause of this? I'm
> > h
On 05/04/11 11:18, Chris Curvey wrote:
> This is on Ubuntu 10.10 server, 64-bit on Intel. I'm running Postgres
> 9.0.3, 64-bit from the ppa repository.
>
> What can I do to help the developers find the root cause of this? I'm
> happy to run a debug version, or find a corefile, or whatever I can
15 matches
Mail list logo