Re: BUG #11867: Strange behaviour with composite types after resetting database tablespace - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #11867: Strange behaviour with composite types after resetting database tablespace
Date
Msg-id 12242.1415125710@sss.pgh.pa.us
Whole thread Raw
In response to BUG #11867: Strange behaviour with composite types after resetting database tablespace  (marc@bloodnok.com)
List pgsql-bugs
marc@bloodnok.com writes:
> I have a script (below) that sets and resets the tablespace for a database
> and drops and recreates a composite type.  The script fails when trying to
> re-create the previously dropped composite type because the type has
> apparently been magically resuscitated by changing the tablespace for the
> database.  I assume this is a bug.

I've confirmed that this patch fixes the described behavior:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=33f80f8480434f02beb940b8f0627d534f3fd3af

            regards, tom lane

pgsql-bugs by date:

Previous
From: Bernd Helmle
Date:
Subject: Re: [HACKERS] COPY TO returning empty result with parallel ALTER TABLE
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] COPY TO returning empty result with parallel ALTER TABLE