> The following bug has been logged online:
> Bug reference: 3774
> Logged by: guillaume (ioguix) de Rorthais
> Email address: ioguix(at)free(dot)fr
> PostgreSQL version: 8.3 beta3
> Operating system: mac os x 10.4.10
> Description: create table like including index doesn't update
> pg_constraints with primary key
> When creating a table using the "create table ... (like ... inluding
> indexes...)" syntaxe, pg_catalog.pg_constraint is not updated with the PK
> constraints which actually is setted in pg_index.
> I'm not sure if this issue is actually a bug or if there a logic behind
> this, but as the primary key is a constraint, I would expect it to be
> in pg_constraint, shouldn't it ?
This can be handled by setting index->isconstraint appropriately inside
The fundamental question though is should we allow primary, unique
CONSTRAINTS which use the index mechanism just as an implementation to be
created using the "INCLUDING INDEXES" mechanism.
As per the discussion here:
maybe we should not?
In other words "INCLUDING INDEXES" should only create those indexes which do
not have isconstraint set to TRUE.
In response to
pgsql-hackers by date
|Next:||From: Brendan Jurd||Date: 2007-11-30 09:14:14|
|Subject: Re: [GENERAL] Empty arrays with ARRAY|
|Previous:||From: Simon Riggs||Date: 2007-11-30 06:31:33|
|Subject: Release Note Changes|
pgsql-bugs by date
|Next:||From: Michailas||Date: 2007-11-30 09:18:23|
|Subject: BUG #3791: Bug in aritmethic calculations|
|Previous:||From: Mike C.||Date: 2007-11-30 01:05:35|
|Subject: BUG #3790: pg_restore error canceling statement due to user request|