"Chris Fischer" <[EMAIL PROTECTED]> writes:
> alter table only t1 add constraint ck_col1 check (number <> 0);
The bug here is that we allow that. Continuing your example,
regression=# insert into t2 values(0);
INSERT 0 1
regression=# select * from t1;
col1
--
0
(1 row)
which sure looks
There's no way in the pg_ tables to identify when a check constraint on
an inherited table should not be inherited. Example:
create table t1 (col1 number(10));
create table t2 () inherits t2;
alter table only t1 add constraint ck_col1 check (number <> 0);
Now, run pg_dump and notice that t
David Darville <[EMAIL PROTECTED]> writes:
> While testing a continuous archiving setup using PostgreSQL 8.2.3, on Debian
> Etch amd64, I found out that the slave database crashed when I did a 'DROP
> DATABASE' on the master.
Thanks for the report. I believe this will fix it:
Index: dbcommands.c
Hello everybody
While testing a continuous archiving setup using PostgreSQL 8.2.3, on Debian
Etch amd64, I found out that the slave database crashed when I did a 'DROP
DATABASE' on the master.
I was trying to stress test our setup, by continuously restoring a dump of
our database, dropping the da
