Re: BUG #3763: crash after create table with primary keydefined

admin(at)abp(dot)pl wrote:
> Dnia Wt Listopada 20 2007, 14:20, Simon Riggs napisał(a):
>> On Tue, 2007-11-20 at 11:46 +0000, Heikki Linnakangas wrote:
>>>>> In logs after this:
>>>>> Nov 20 11:02:04 www postgres[32757]: [4-1] wolni>NOTICE: CREATE
>>> TABLE /
>>>>> PRIMARY KEY will create implicit index "phpbb_acl_roles_data_pkey"
>>> for
>>>>> table
>>>>> Nov 20 11:02:04 www postgres[32731]: [2-1] >LOG: server process (PID
>>> 32757)
>>>>> was terminated by signal 11
>>
>>> To me it does look like it was the CREATE TABLE that crashed. The NOTICE
>>> shows that it's process ID 32757 that's running the CREATE TABLE, and
>>> the LOG line later on says that that's the process that crashed.
>> Yep, agreed. :-(
>>
> OK so what we can do now?

Do you have core file? It is usually stored in data postgreSQL
directory. Can you provide stack trace to determine which function
fails? It is very important.

what's happen when you create primary key by alter table command?

what's happen when you create unique index on (role_id, auth_option_id)?

Is it fresh database? Can you reproduce it on the same machine with the
same postgreSQL installation on new created database cluster?

Zdenek