Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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.M. 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: Fri, 28 Jul 2006 00:10:58 -0400
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
- References:
- Re: [SQL] PostgreSQL server terminated by signal 11
- From: Daniel CAUNE
- Re: [SQL] PostgreSQL server terminated by signal 11
- Prev by Date: Re: [SQL] PostgreSQL server terminated by signal 11
- Next by Date: facing problem with CVS access
- Previous by thread: Re: [SQL] PostgreSQL server terminated by signal 11
- Next by thread: Re: [SQL] PostgreSQL server terminated by signal 11
- Indexes: