Re: [HACKERS] current segfault if autovauum is on

2006-03-08 Thread Alvaro Herrera
Gourish Singbal wrote: > Just Curious, which postgresql server version bug has been fixed ?. is it > existing on 8.1.3 and under which circumstances ?. No, this particular bug existed only on the CVS HEAD branch, as it was introduced there recently. -- Alvaro Herrera

Re: [HACKERS] current segfault if autovauum is on

2006-03-07 Thread Gourish Singbal
  Just Curious, which postgresql server version bug has been fixed ?. is it existing on 8.1.3 and under which circumstances ?.  On 3/7/06, Tom Lane <[EMAIL PROTECTED]> wrote: Tatsuo Ishii <[EMAIL PROTECTED]> writes:> It seems I get a segfault in backend if autovacuum is enabled. Fixed, thanks for r

Re: [HACKERS] current segfault if autovauum is on

2006-03-07 Thread Tom Lane
Tatsuo Ishii <[EMAIL PROTECTED]> writes: > It seems I get a segfault in backend if autovacuum is enabled. Fixed, thanks for report. regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space m

[HACKERS] current segfault if autovauum is on

2006-03-07 Thread Tatsuo Ishii
It seems I get a segfault in backend if autovacuum is enabled. Here is the backtrace when I connect to backend by using psql: Program received signal SIGSEGV, Segmentation fault. 0x081fe737 in AtEOXact_GUC (isCommit=1 '\001', isSubXact=0 '\0') at guc.c:3139 3139if (stack->nest_