From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel CAUNE <d.caune@free.fr>
Cc: 'D'Arcy J.M. Cain' <darcy@druid.net>
Cc: 'Daniel Caune' <daniel.caune@ubisoft.com>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] PostgreSQL server terminated by signal 11
Date: Fri, 28 Jul 2006 00:10:58 -0400
Message-ID: <16121.1154059858@sss.pgh.pa.us> (raw)
In-Reply-To: <0J33006NWI0FI840@VL-MO-MR003.ip.videotron.ca>
References: <0J33006NWI0FI840@VL-MO-MR003.ip.videotron.ca>
Daniel CAUNE <d.caune@free.fr> writes:
> Actually it seems, from the source code, that a null slot->tts_tuple
> won't lead to a segmentation fault in function slot_attisnull, while
> slot and slot->tts_tupleDescriptor will.
I'll bet on D'Arcy's theory that slot is being passed in as NULL.
Exactly why remains to be seen ... we need that stack trace!
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, d.caune@free.fr, darcy@druid.net, daniel.caune@ubisoft.com, pgsql-admin@postgresql.org
Subject: Re: [SQL] PostgreSQL server terminated by signal 11
In-Reply-To: <16121.1154059858@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox