I'm just doing insert statements via JDBC. Here's the table definition:
CREATE TABLE collection
(
id serial NOT NULL,
app_uid character(36) NOT NULL DEFAULT uuid_generate_v4(),
lock_rev integer NOT NULL DEFAULT 0,
collection_type_code character(3) NOT NULL,
asset_type_code character(3) NOT NULL,
code character varying(10),
"name" character varying(128) NOT NULL,
title_prefix character varying(128),
item_count integer,
is_fixed_count boolean NOT NULL DEFAULT false,
is_active boolean NOT NULL DEFAULT true,
CONSTRAINT pk_collection PRIMARY KEY (id),
CONSTRAINT collection_collection_type_code_fkey FOREIGN KEY
(collection_type_code)
REFERENCES collection_type (code) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION,
CONSTRAINT collection_type_code_fkey FOREIGN KEY (asset_type_code)
REFERENCES asset_type (code) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION,
CONSTRAINT collection_app_uid_key UNIQUE (app_uid)
)
WITH (
OIDS=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 0=
xC0000005
>> 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
>
