-Message d'origine-
De : Tom Lane [mailto:[EMAIL PROTECTED]
Envoyé : jeudi, juillet 27, 2006 19:26
À : Daniel Caune
Cc : pgsql-admin@postgresql.org; pgsql-sql@postgresql.org
Objet : Re: [SQL] PostgreSQL server terminated by signal 11
Daniel Caune [EMAIL PROTECTED] writes:
I
Daniel Caune [EMAIL PROTECTED] writes:
Program received signal SIGSEGV, Segmentation fault.
0x08079e2a in slot_attisnull ()
(gdb) bt
#0 0x08079e2a in slot_attisnull ()
#1 0x0807a1d0 in slot_getattr ()
#2 0x080c6c73 in FormIndexDatum ()
#3 0x080c6ef1 in IndexBuildHeapScan ()
#4
De : Tom Lane [mailto:[EMAIL PROTECTED]
Envoyé : vendredi, juillet 28, 2006 09:38
À : Daniel Caune
Cc : pgsql-admin@postgresql.org; pgsql-sql@postgresql.org
Objet : Re: [SQL] PostgreSQL server terminated by signal 11
Daniel Caune [EMAIL PROTECTED] writes:
Program received signal SIGSEGV
Daniel Caune [EMAIL PROTECTED] writes:
The statement copy gslog_event to stdout; leads to ERROR: invalid memory
alloc request size 4294967293 after awhile.
...
I did other tests on some other tables that contain less data but that seem
also corrupted:
This is a bit scary as it suggests a
Hi,
My PostgreSQL server running on a Linux machine is
terminated by signal 11 whenever I try to create some indexes on a table, which
contains quite a lot of data. However I succeeded in creating some other indexes
without having the PostgreSQL server terminated:
agora= CREATE INDEX
On Thu, 27 Jul 2006, Daniel Caune wrote:
My PostgreSQL server running on a Linux machine is terminated by signal
11 whenever I try to create some indexes on a table, which contains
quite a lot of data. However I succeeded in creating some other indexes
without having the PostgreSQL server
Daniel Caune [EMAIL PROTECTED] writes:
My PostgreSQL server running on a Linux machine is terminated by signal
11 whenever I try to create some indexes on a table, which contains
quite a lot of data.
Judging from your examples it's got something to do with the partial
index WHERE clause. What
De : Tom Lane [mailto:[EMAIL PROTECTED]
Envoyé : jeudi, juillet 27, 2006 16:06
À : Daniel Caune
Cc : pgsql-sql@postgresql.org
Objet : Re: [SQL] PostgreSQL server terminated by signal 11
Daniel Caune [EMAIL PROTECTED] writes:
My PostgreSQL server running on a Linux machine is terminated
-Message d'origine-
De : Tom Lane [mailto:[EMAIL PROTECTED]
Envoyé : jeudi, juillet 27, 2006 16:06
À : Daniel Caune
Cc : pgsql-sql@postgresql.org
Objet : Re: [SQL] PostgreSQL server terminated by signal 11
Daniel Caune [EMAIL PROTECTED] writes:
My PostgreSQL server running
Daniel Caune [EMAIL PROTECTED] writes:
I run the command responsible for creating the index and I entered continue
in gdb for executing the command. After a while, the server crashes:
Program received signal SIGSEGV, Segmentation fault.
0x08079e2a in slot_attisnull ()
(gdb)
On Thu, 27 Jul 2006 19:00:27 -0400
Daniel Caune [EMAIL PROTECTED] wrote:
I run the command responsible for creating the index and I entered continue
in gdb for executing the command. After a while, the server crashes:
Program received signal SIGSEGV, Segmentation fault.
0x08079e2a in
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
De la part de Tom Lane
Envoyé : jeudi 27 juillet 2006 19:26
À : Daniel Caune
Cc : pgsql-admin@postgresql.org; pgsql-sql@postgresql.org
Objet : Re: [SQL] PostgreSQL server terminated by signal 11
Daniel Caune
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
De la part de D'Arcy J.M. Cain
Envoyé : jeudi 27 juillet 2006 19:49
À : Daniel Caune
Cc : [EMAIL PROTECTED]; pgsql-admin@postgresql.org; pgsql-
[EMAIL PROTECTED]
Objet : Re: [SQL] PostgreSQL server terminated
Daniel CAUNE [EMAIL PROTECTED] 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
14 matches
Mail list logo
