Re: [SQL] PostgreSQL server terminated by signal 11

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel CAUNE <d(dot)caune(at)free(dot)fr>
Cc: "'D'Arcy J(dot)M(dot) Cain'" <darcy(at)druid(dot)net>, "'Daniel Caune'" <daniel(dot)caune(at)ubisoft(dot)com>, pgsql-admin(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org
Subject: Re: [SQL] PostgreSQL server terminated by signal 11
Date: 2006-07-28 04:10:58
Message-ID: 16121.1154059858@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-sql

Daniel CAUNE <d(dot)caune(at)free(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message saurabh 2006-07-28 09:09:36 facing problem with CVS access
Previous Message Daniel CAUNE 2006-07-28 04:05:06 Re: [SQL] PostgreSQL server terminated by signal 11

Browse pgsql-sql by date

  From Date Subject
Next Message Manlio Perillo 2006-07-28 08:37:28 primary keys as TEXT
Previous Message Daniel CAUNE 2006-07-28 04:05:06 Re: [SQL] PostgreSQL server terminated by signal 11