Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-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

pgsql-admin by date

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

pgsql-sql by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group