From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dennis Noordsij <dennis(dot)noordsij(at)helsinki(dot)fi>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4793: Segmentation fault when doing vacuum analyze |
Date: | 2009-05-05 14:46:29 |
Message-ID: | 4A005145.7000509@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tom Lane wrote:
> "Dennis Noordsij" <dennis(dot)noordsij(at)helsinki(dot)fi> writes:
>> (gdb) bt
>> #0 0x00000000004eecf7 in compute_scalar_stats (stats=0x1abd878,
>> fetchfunc=0x4f0f30 <std_fetch_func>, samplerows=<value optimized out>,
>> totalrows=4154315)
>> at analyze.c:2321
>> #1 0x00000000004efbf5 in analyze_rel (relid=16484, vacstmt=0x1aaf140,
>> bstrategy=<value optimized out>, update_reltuples=1 '\001') at
>> analyze.c:433
>
> Hmm, that code hasn't changed in quite some time, so I doubt this is a
> new bug in 8.4. You'll need to either poke into it yourself, or supply
> a dump of the table to someone who can.
hmm not sure if it is related in any way - but setting statistics to >
1000 is "new" in 8.4...
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-05-05 15:14:20 | Re: BUG #4793: Segmentation fault when doing vacuum analyze |
Previous Message | Dennis Noordsij | 2009-05-05 14:21:33 | Re: BUG #4793: Segmentation fault when doing vacuum analyze |