; the crash was
disappeared.
I think the bug is resolved.
Thx for great support.
Andrea Peri.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
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;
Hi,
I have some update on the crash of pg9.0.
seem that PG9 will crash even on windows 32bit.
But meanwhile in win7-64 bit crash always at first try, in win7 32bit it
crash
from first and second time after restart.
As report here from Postgis Team.
http://postgis.refractions.net/pipermail/p
s needed the instruction of
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows#Remote_debugging_with_windbg.exe
Regards,
Andrea Peri.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
your case, as the backend is crashing you will want to use windbg or
Visual Studio Express Edition to collect the crash data; process explorer
will not be enough.
ok, now I try to do this backtrace.
Regards,
Andrea.
2010/10/3 Craig Ringer
> On 2/10/2010 9:08 PM, Andrea Peri wrote:
he same windows machine) using
the postgres 8.4.4 istance and all terminated without any problem.
The procedure is substantially only a huge list of
string sql like
insert into()
executed one by one in many tables and with autocommit.
Andrea Peri.
--
---------
Andrea Peri
. . . . .
