Re: Possible bug in PostgreSQL 8.3beta4 (postgres process segfaults)

From: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
To: "Lawrence Oluyede" <l(dot)oluyede(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Possible bug in PostgreSQL 8.3beta4 (postgres process segfaults)
Date: 2007-12-12 12:29:42
Message-ID: 162867790712120429q2b16801m6aba709c3a572030@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello

I cannot repeat this bug on my test date. Can you send some small set
that reproduce the bug?

Regards
Pavel

On 12/12/2007, Lawrence Oluyede <l(dot)oluyede(at)gmail(dot)com> wrote:
> Here it is:
>
> postgres$ gdb /usr/local/pgsql/bin/postgres core.1600
> (gdb) bt
> #0 0x082c101c in pfree (pointer=0x8472f00) at mcxt.c:591
> #1 0xb7e46513 in xmlCleanupCharEncodingHandlers () from /usr/lib/libxml2.so.2
> #2 0xb7e4f091 in xmlCleanupParser () from /usr/lib/libxml2.so.2
> #3 0x082940e4 in xpath (fcinfo=0xbfee59c4) at xml.c:3441
> #4 0x0817107f in ExecMakeFunctionResult (fcache=0x84723d0,
> econtext=0x8472348, isNull=0x8472fa8 "", isDone=0x8472fb8) at
> execQual.c:1351
> #5 0x0816f522 in ExecProject (projInfo=0x8472e98, isDone=0xbfee5c78)
> at execQual.c:4601
> #6 0x08175987 in ExecScan (node=0x84722c0, accessMtd=0x817e310
> <IndexNext>) at execScan.c:143
> #7 0x0817e2e7 in ExecIndexScan (node=0x84722c0) at nodeIndexscan.c:147
> #8 0x0816ee7a in ExecProcNode (node=0x84722c0) at execProcnode.c:338
> #9 0x0816e113 in ExecutorRun (queryDesc=0x845e908,
> direction=ForwardScanDirection, count=0) at execMain.c:1233
> #10 0x08204ea0 in PortalRunSelect (portal=0x84577a0, forward=<value
> optimized out>, count=0, dest=0x845d1c8) at pquery.c:943
> #11 0x08205eaa in PortalRun (portal=0x84577a0, count=2147483647,
> isTopLevel=1 '\001', dest=0x845d1c8, altdest=0x845d1c8,
> completionTag=0xbfee5ee8 "") at pquery.c:797
> #12 0x082013c3 in exec_simple_query (
> query_string=0x8453790 "SELECT xpath('//sp:description/text()',
> content, ARRAY[ARRAY['sp',
> 'http://www.statpro.net/xml/structure/1.0']])\n FROM instrument
> WHERE code = 'TEST0018';") at postgres.c:963
> #13 0x08202ebc in PostgresMain (argc=4, argv=<value optimized out>,
> username=0x83d2330 "postgres") at postgres.c:3531
> #14 0x081d76cf in ServerLoop () at postmaster.c:3180
> #15 0x081d83a5 in PostmasterMain (argc=3, argv=0x83ccb08) at postmaster.c:1028
> #16 0x081909a0 in main (argc=3, argv=0x82c0c00) at main.c:188
> (gdb) l
> 586 header = (StandardChunkHeader *)
> 587 ((char *) pointer - STANDARDCHUNKHEADERSIZE);
> 588
> 589 AssertArg(MemoryContextIsValid(header->context));
> 590
> 591 (*header->context->methods->free_p) (header->context, pointer);
> 592 }
> 593
> 594 /*
> 595 * repalloc
>
> I also uploaded the entire core file on the net, if you want to inspect it:
> http://www.oluyede.org/temp/core.1600 (it's ~ 30M)
>
> thank you
>
>
>
> --
> Lawrence, oluyede.org - neropercaso.it
> "It is difficult to get a man to understand
> something when his salary depends on not
> understanding it" - Upton Sinclair
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2007-12-12 12:30:18 Re: Possible bug in PostgreSQL 8.3beta4 (postgres process segfaults)
Previous Message Enrico Sirola 2007-12-12 12:27:30 index organized tables use case