Re: Postgres 9.0 crash on win7

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: Andrea Peri <aperi2007(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Postgres 9.0 crash on win7
Date: 2010-10-05 02:02:49
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> After turning autovacuum off completely, though, it does crash when
> ANALYZE is run.

>> postgres.exe!pfree(void * pointer=0x68f08610) Line 591 + 0x3 bytes C
>> postgres.exe!examine_attribute(RelationData * onerel=0x00000000, int attnum=5, Node * index_expr=0x00000000) Line 877 C
>> postgres.exe!do_analyze_rel(RelationData * onerel=0x01747b48, VacuumStmt * vacstmt=0x01690580, char update_reltuples='', char inh=0) Line 357 + 0xa bytes C

Hmm. That is suspiciously close to the location of some last-minute
changes in Postgres 9.0. I wonder whether Andrea is using a version of
PostGIS that was compiled against pre-9.0RC1 Postgres sources. If they
weren't accounting for this patch:;a=commitdiff;h=67becf8d41a082eaaf6db6e0860d49409b79e32b
then we could easily have a crash right about here --- in fact it looks
like this is exactly what you'd get, because the extension would think
that the compute_stats field is where attrtype now is, so the
"pfree(stats->attrtype)" would be trying to pfree a function address.

In short, what we've got here is a version skew problem. That doubtless
explains why Craig couldn't duplicate it on his Linux machine.

regards, tom lane

In response to


Browse pgsql-bugs by date

  From Date Subject
Next Message Craig Ringer 2010-10-05 02:51:18 Re: Postgres 9.0 crash on win7
Previous Message Craig Ringer 2010-10-05 01:26:16 Re: Postgres 9.0 crash on win7