"Dennis Noordsij" <dennis.noord...@helsinki.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.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
