[BUGS] BUG #6712: PostgreSQL 9.2 beta2: alter table drop constraint does not work on inherited master table

2012-06-30 Thread miroslav . sulc
The following bug has been logged on the website: Bug reference: 6712 Logged by: Miroslav Ć ulc Email address: miroslav.s...@fordfrog.com PostgreSQL version: Unsupported/Unknown Operating system: Gentoo Linux Description: here is the test case: test=# create table tes

Re: [BUGS] BUG #6706: pg_upgrade fails when plpgsql dropped/re-created

2012-06-30 Thread Tom Lane
Bruce Momjian writes: > On Fri, Jun 29, 2012 at 11:35:15PM -0400, Tom Lane wrote: >> I think you're misjudging the core of the issue. The same thing >> would happen if somebody dropped and recreated the public schema. >> Or anything else that we create at initdb time but allow to be >> dropped.

Re: [BUGS] BUG #6706: pg_upgrade fails when plpgsql dropped/re-created

2012-06-30 Thread Bruce Momjian
On Sat, Jun 30, 2012 at 11:12:56AM -0400, Tom Lane wrote: > Bruce Momjian writes: > > On Fri, Jun 29, 2012 at 11:35:15PM -0400, Tom Lane wrote: > >> I think you're misjudging the core of the issue. The same thing > >> would happen if somebody dropped and recreated the public schema. > >> Or anyth

Re: [BUGS] BUG #6706: pg_upgrade fails when plpgsql dropped/re-created

2012-06-30 Thread Tom Lane
Bruce Momjian writes: > On Sat, Jun 30, 2012 at 11:12:56AM -0400, Tom Lane wrote: >> Did it restore the nonstandard ownership of the schema? > No --- drop/create of the public schema produces: > ... > However, surprisingly, a simple pg_dump/restore also does not preserve > the public schema permi