Re: BUG #5269: postgres backend terminates with SIGSEGV

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Justin Pitts" <justinpitts(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Subject: Re: BUG #5269: postgres backend terminates with SIGSEGV
Date: 2010-01-09 04:04:55
Message-ID: 28098.1263009895@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Justin Pitts" <justinpitts(at)gmail(dot)com> writes:
> [ crash in CopySnapshot ]

This is a new one I think. Alvaro fixed some snapshot management issues
back in October, but if you're seeing it on 8.4.2 then that didn't fix
it :-(

> I am including a backtrace. Sanitizing a simple, clear repro case will take
> us some time, and it may be easier for us to host a duplicate machine for
> someone to ssh into. Please let me know if that is reasonable, or how else I
> can assist.

The trace is definitely not sufficient info by itself. If you'd prefer
to make a machine available than extract a test case, we can work with
that. Contact me or Alvaro offlist to work out details.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message beulah prasanthi 2010-01-09 07:36:05 could not open server file
Previous Message Justin Pitts 2010-01-09 03:50:38 BUG #5269: postgres backend terminates with SIGSEGV