[BUGS] I find a bug (IMHO)

[Danger Dancer]

Sorry for my bad English.
The report in the attach
If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to [EMAIL PROTECTED]

To report any other bug, fill out the form below and e-mail it to
[EMAIL PROTECTED]

If you not only found the problem but solved it and generated a patch
then e-mail it to [EMAIL PROTECTED] instead.  Please use the
command "diff -c" to generate the patch.

You may also enter a bug report at http://www.postgresql.org/ instead of
e-mail-ing this form.


POSTGRESQL BUG REPORT TEMPLATE



Your name   :   Roman
Your email address  :   [EMAIL PROTECTED]


System Configuration
-
  Architecture (example: Intel Pentium) : Intel Celeron 667

  Operating System (example: Linux 2.0.26 ELF)  : Linux 2.4.18 (Red Hat 7.3)

  PostgreSQL version (example: PostgreSQL-7.4):   PostgreSQL-7.4

  Compiler used (example:  gcc 2.95.2)  : gcc 2.97


Please enter a FULL description of your problem:

Sorry, my English very bad, but i try write it
The pg_dump not save changes as ALTER TABLE DROP CONSTRAINT in case with inheritans 
table


Please describe a way to repeat the problem.   Please try to provide a
concise reproducible example, if at all possible: 
--
#little example
create table a (d int check (d<5));
create table b () inherits (a);
alter table b drop constraint "a_d";
#after it, table b not have any constraint. Try save and restore the structure of 
database
#in shell:
pg_dump -s -f ~/dbtest -U postgres test
#in psql:
drop database test;
create database test;
#in shell:
psql test postgres < ~/dbtest
#Now, table b have constraint "a_d" :(



If you know how this problem might be fixed, list the solution below:
-
I don't know :(


---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

Re: [BUGS] I find a bug (IMHO)

[Tom Lane]

Danger Dancer <[EMAIL PROTECTED]> writes:
> #little example
> create table a (d int check (d<5));
> create table b () inherits (a);
> alter table b drop constraint "a_d";

I think the bug is that it allowed you to do this.  You should not be
able to drop an inherited constraint, any more than you can drop an
inherited column.

regards, tom lane

---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match

Re: [BUGS] Probably a security bug in PostgreSQL rule system

[Tom Lane]

"Sergey N. Yatskevich" <[EMAIL PROTECTED]> writes:
> Next -- test and it's output, that shows, that if view has INSERT,
> UPDATE and DELETE rules then _ANY_ user can insert, update and delete
> data in tables, that affected by this rules even user has no INSERT,
> UPDATE and DELETE privileges on view and table.

> This problem exists for at least 7.3.4 and 7.4.1 PostgreSQL versions.

I think this is the same issue discussed in this thread:
http://archives.postgresql.org/pgsql-general/2003-12/msg00551.php
and continued here:
http://archives.postgresql.org/pgsql-hackers/2003-12/msg00743.php
It's from an erroneous fix in 7.3.3 for another bug.  We'll probably
have to revert that patch and try again in 7.5.

regards, tom lane

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]