Re: BUG #5669: server process was terminated by exception 0xC0000005

Running the server in debug mode, I see the following before the
server crashes -- it looks like something goes wrong with
autovac_balance_cost when trying to analyze the collection table (that
was the table the inserts were being done into).

Thanks
Andrew

2010-09-21 16:27:40 EDTDEBUG:  collection: vac: 0 (threshold 50), anl:
76 (threshold 50)
2010-09-21 16:27:40 EDTDEBUG:  autovac_balance_cost(pid=3D5896
db=3D4329981, rel=3D4331344, cost_limit=3D200, cost_delay=3D20)
2010-09-21 16:27:40 EDTDEBUG:  CommitTransaction
2010-09-21 16:27:40 EDTDEBUG:  name: unnamed; blockState:
STARTED; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
2010-09-21 16:27:40 EDTDEBUG:  StartTransaction
2010-09-21 16:27:40 EDTDEBUG:  name: unnamed; blockState:
DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
2010-09-21 16:27:40 EDTDEBUG:  analyzing "public.collection"
2010-09-21 16:27:41 EDTDEBUG:  reaping dead processes
2010-09-21 16:27:41 EDTDEBUG:  server process (PID 5896) was
terminated by exception 0xC0000005
2010-09-21 16:27:41 EDTHINT:  See C include file "ntstatus.h" for a
description of the hexadecimal value.
2010-09-21 16:27:41 EDTLOG:  server process (PID 5896) was terminated
by exception 0xC0000005
2010-09-21 16:27:41 EDTHINT:  See C include file "ntstatus.h" for a
description of the hexadecimal value.
2010-09-21 16:27:41 EDTLOG:  terminating any other active server processes

On Tue, Sep 21, 2010 at 3:12 PM, Andrew Geery <andrew.geery@gmail.com> wrot=
e:
> I'm just doing insert statements via JDBC. =A0Here's the table definition:
>
> CREATE TABLE collection
> (
> =A0id serial NOT NULL,
> =A0app_uid character(36) NOT NULL DEFAULT uuid_generate_v4(),
> =A0lock_rev integer NOT NULL DEFAULT 0,
> =A0collection_type_code character(3) NOT NULL,
> =A0asset_type_code character(3) NOT NULL,
> =A0code character varying(10),
> =A0"name" character varying(128) NOT NULL,
> =A0title_prefix character varying(128),
> =A0item_count integer,
> =A0is_fixed_count boolean NOT NULL DEFAULT false,
> =A0is_active boolean NOT NULL DEFAULT true,
> =A0CONSTRAINT pk_collection PRIMARY KEY (id),
> =A0CONSTRAINT collection_collection_type_code_fkey FOREIGN KEY
> (collection_type_code)
> =A0 =A0 =A0REFERENCES collection_type (code) MATCH SIMPLE
> =A0 =A0 =A0ON UPDATE NO ACTION ON DELETE NO ACTION,
> =A0CONSTRAINT collection_type_code_fkey FOREIGN KEY (asset_type_code)
> =A0 =A0 =A0REFERENCES asset_type (code) MATCH SIMPLE
> =A0 =A0 =A0ON UPDATE NO ACTION ON DELETE NO ACTION,
> =A0CONSTRAINT collection_app_uid_key UNIQUE (app_uid)
> )
> WITH (
> =A0OIDS=3DFALSE
> );
>
> Thanks
> Andrew
>
> On Tue, Sep 21, 2010 at 3:00 PM, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.com> wrote:
>> On 21/09/10 21:57, Andrew Geery wrote:
>>>
>>> The following bug has been logged online:
>>>
>>> Bug reference: =A0 =A0 =A05669
>>> Logged by: =A0 =A0 =A0 =A0 =A0Andrew Geery
>>> Email address: =A0 =A0 =A0andrew.geery@gmail.com
>>> PostgreSQL version: 9.0
>>> Operating system: =A0 Windows Vista
>>> Description: =A0 =A0 =A0 =A0server process was terminated by exception =
0xC0000005
>>> Details:
>>>
>>> My PG 9.0 DB (EnterpriseDB edition 32-bit) on Windows Vista SP1 crashes
>>> pretty predictably.
>>>
>>> I executed some SQL and the server crashes.
>>>
>>> Actually, the SQL completes successfully and then the server crashes.
>>
>> What's the query that causes the crash?
>>
>> --
>> =A0Heikki Linnakangas
>> =A0EnterpriseDB =A0 http://www.enterprisedb.com
>>
>