Re: 73.5 and uw 713

Hi Tom,

At last I have a much better trace for the vacuum full bug.

Can some one help me on this one?

Image mémoire de postmaster (processus p1) créée
FICHIER IMAGE MEMOIRE [swapn dans qsort.c]
11 (segv code[SEGV_MAPERR] address[0x8420000]) SIGNALE dans p1
0xbffae03f (swapn+47:) movl (%esi),%eax
debug> Suivi de pile correspondant à p1, Programme postmaster
*[0] swapn(0x2, 0x831b758, 0x831b770) [0xbffae03f]
[1] qst(0x80448cc, 0x831b758, 0x831b788) [0xbffadca2]
[2] qsort(0x831b758, 0x18, 0x2, 0x80eb9f8) [0xbffae17f]
[3] repair_frag(vacrelstats=0x83122bc, onerel=0x82cf56c, vacuum_pages=0x8046a64, fraged_pages=0x8046a54, nindexes=1, Irel=0x83672e0) [vacuum(dot)c(at)2227]
[4] full_vacuum_rel(onerel=0x82cf56c, vacstmt=0x83104b4) [vacuum(dot)c(at)955]
[5] vacuum_rel(relid=16408, vacstmt=0x83104b4, expected_relkind=114 (or 'r')) [vacuum(dot)c(at)827]
[6] vacuum(vacstmt=0x83104b4) [vacuum(dot)c(at)290]
[7] ProcessUtility(parsetree=0x83104b4, dest=Remote, completionTag="") [utility(dot)c(at)gram(dot)y@713]
[8] pg_exec_query_string(query_string=0x831020c, dest=Remote, parse_context=0x830e204) [postgres(dot)c(at)gram(dot)y@789]
[9] PostgresMain(argc=4, argv=0x8046d78, username="ohp") [postgres(dot)c(at)gram(dot)y@2013]
[10] DoBackend(port=0x829e500) [postmaster(dot)c(at)2310]
[11] BackendStartup(port=0x829e500) [postmaster(dot)c(at)1932]
[12] ServerLoop( présumé: 0x1, 0x8297af8, 0x1) [postmaster(dot)c(at)1009]
[13] PostmasterMain(argc=1, argv=0x8297af8) [postmaster(dot)c(at)788]
[14] main(argc=1, argv=0x8047c44, 0x8047c4c) [main(dot)c(at)210]
[15] _start() [0x806ad1c]
debug>

On Mon, 8 Dec 2003, Tom Lane wrote:

> Date: Mon, 08 Dec 2003 14:03:42 -0500
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> To: ohp(at)pyrenet(dot)fr
> Cc: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
> Subject: Re: [HACKERS] 73.5 and uw 713
>
> ohp(at)pyrenet(dot)fr writes:
> > I've upgraded my system from 7.3.4 to 7.3.5 yesterday and have already
> > experienced to crash during vacuum full.
> > I have'nt recompiled with debug yet but it's a sigsegv in function
> > repair_frag in vacuum.c
>
> Considering that vacuum.c hasn't changed in that branch since 7.3beta4,
> it's highly unlikely that this represents a regression between 7.3.4 and
> 7.3.5. Pre-existing bug, maybe ...
>
> regards, tom lane
>

--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
6, Chemin d'Harraud Turrou +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: ohp(at)pyrenet(dot)fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)