Hi,
I have do some other test.
I set
autovacuum = off.
With this setting the server don't crash.
But certainly something go bad.
Infact
if (after run the query) I connect with posql as user 'postgres' and try
a single command
VACUUM;
nothing happened.
But if I try a
single command
ANALYZE;
the server crash istantly.
After this I restart the server and
re-try reconnecting to PG9 but without re-run the query script.
again
if a run
ANALYZE the server crash.
I think the script has insert write something wrong in a table and after
this insert.
Always time someone (autovacuum or user) try an analyze
this cause the crash.
however seem to be the analyze to do the crash, not the vacuum.
Perhaps to problem is in the INSERT INTO.
that put sometime that the old PG8.4.4 can understand and use, meanwhile
PG) don't understand or is not capable to use.
for example, I use often some field of big size:
VARCHAR(200000)
the next try I do is to remove the postgis components to see if again
this happened.
Andrea.
Il 04/10/2010 04:56, Tom Lane ha scritto:
> Craig Ringer<craig@postnewspapers.com.au> writes:
>> While it's consistently crashing my Pg 9 on win7 32-bit, too, I haven't
>> been able to get a backtrace yet. I thought it'd be trivial given the
>> ease of reproducing the crash - but the process that's crashing isn't
>> the backend running the query.
>> It looks like it's one of the helpers like the stats collector, autovac,
>> bgwriter, etc. I'm unsure which yet.
> I'd bet on autovacuum. You might be able to reproduce the crash in the
> foreground process by issuing a manual VACUUM or ANALYZE.
>
> regards, tom lane
>