Re: Postgres 9.0 crash on win7
От | Craig Ringer |
---|---|
Тема | Re: Postgres 9.0 crash on win7 |
Дата | |
Msg-id | 4CA7F39B.5080002@postnewspapers.com.au обсуждение исходный текст |
Ответ на | Postgres 9.0 crash on win7 (Andrea Peri <aperi2007@gmail.com>) |
Ответы |
Re: Postgres 9.0 crash on win7
|
Список | pgsql-bugs |
On 2/10/2010 9:08 PM, Andrea Peri wrote: > Hi, > > I'm using usually > Postgres 8.4.4 (32bit) + Postgis 1.5.1 on Windows7 64bit. > > Now I try-ing the last > Postgres 9.0 (32bit) + Postgis 1.5.2 on the same machine (win7 64bit). > > I experience a > > crash of Postgres while it is running a huge load of data. Does that include PostGIS datatypes? > 2010-10-01 22:44:20 CEST LOG: server process (PID 2540) was terminated > by exception 0xC0000005 That's invalid memory access - like a UNIX segfault (sig11). Can you show your schema - the definition of the table(s) involved in the INSERT and any triggers on them? The output of: \d+ tablename from psql would do the trick. Truly, the most helpful thing at this point would be to collect a backtrace showing where in the postgresql server it crashed. There are instructions on how to do that here: http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows In 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. -- Craig Ringer Tech-related writing at http://soapyfrogs.blogspot.com/
В списке pgsql-bugs по дате отправления: