Re: [HACKERS] CREATE TABLE ... PRIMARY KEY kills backend - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] CREATE TABLE ... PRIMARY KEY kills backend
Date
Msg-id 7843.947635740@sss.pgh.pa.us
Whole thread Raw
In response to CREATE TABLE ... PRIMARY KEY kills backend  ("Oliver Elphick" <olly@lfix.co.uk>)
Responses Re: [HACKERS] CREATE TABLE ... PRIMARY KEY kills backend
List pgsql-hackers
"Oliver Elphick" <olly@lfix.co.uk> writes:
> Using the cvs version updated this morning, this query kills the backend,
> with no explanation in the log (-d 3):
>
>   create table junk (id char(4) primary key, name text not null)

Works for me:

regression=# create table junk (id char(4) primary key, name text not null);
NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 'junk_pkey' for table 'junk'
CREATE

Are you sure you have a complete update of the INDEX_MAX_KEYS changes?
I committed the last of them about 1am EST (6am GMT) this morning, and
it was a change to config.h.in ---- you would need to do a *full*
configure, build, initdb cycle to be sure you have working code.

If that doesn't do it for you, there may be a platform-dependent bug
still lurking; can you provide a debugger backtrace of the crashed
backend?

I'd also suggest running the regress tests ... they pass here, with
the exception of the 'array' test ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] CREATE TABLE ... PRIMARY KEY kills backend
Next
From: Don Baccus
Date:
Subject: bug in 6.5.3...