On Thu, Aug 19, 2010 at 5:19 PM, Tom Lane wrote:
> Thue Janus Kristensen writes:
> > I finally succeeded in creating a test case, after much experimentation.
> > Running the attached sql crashes my postgresql server 100% of the time.
>
> Cute problem.
Generating the test case was very "interes
Thue Janus Kristensen writes:
> I finally succeeded in creating a test case, after much experimentation.
> Running the attached sql crashes my postgresql server 100% of the time.
Cute problem. The attached fix cures it for me; would you see if it
solves your original case too?
Thue Janus Kristensen writes:
> I finally succeeded in creating a test case, after much experimentation.
> Running the attached sql crashes my postgresql server 100% of the time.
Cool, replicated here on CVS HEAD:
Program terminated with signal 10, Bus error.
#0 afterTriggerCheckState (evtshare
I finally succeeded in creating a test case, after much experimentation.
Running the attached sql crashes my postgresql server 100% of the time.
Regards, Thue
On Tue, Aug 17, 2010 at 11:32 PM, Robert Haas wrote:
> On Tue, Aug 17, 2010 at 5:26 PM, Thue Janus Kristensen
> wrote:
> >
> > The foll
On Tue, Aug 17, 2010 at 10:55 PM, Craig Ringer
wrote:
> On 18/08/10 05:26, Thue Janus Kristensen wrote:
>> /var/log/syslog:
>> Aug 17 23:08:26 thue-laptop kernel: [46188.626357] postgres[11461]: segfault
>> at 21723858 ip 00772286 sp bf8a4a80 error 4 in postgres[621000+446000]
>
> If you're game,
On 18/08/10 05:26, Thue Janus Kristensen wrote:
> /var/log/syslog:
> Aug 17 23:08:26 thue-laptop kernel: [46188.626357] postgres[11461]: segfault
> at 21723858 ip 00772286 sp bf8a4a80 error 4 in postgres[621000+446000]
If you're game, it might also be useful to see what the backend was up
to when
On Tue, Aug 17, 2010 at 5:26 PM, Thue Janus Kristensen wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5622
> Logged by: Thue Janus Kristensen
> Email address: thu...@gmail.com
> PostgreSQL version: 8.4.4
> Operating system: Ubuntu 10.04 LTS i386
> Desc
