Re: BUG #11867: Strange behaviour with composite types after resetting database tablespace

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: marc(at)bloodnok(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #11867: Strange behaviour with composite types after resetting database tablespace
Date: 2014-11-04 18:28:30
Message-ID: 12242.1415125710@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

marc(at)bloodnok(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-11-04 18:51:23 Re: [HACKERS] COPY TO returning empty result with parallel ALTER TABLE
Previous Message Bernd Helmle 2014-11-04 18:23:21 Re: COPY TO returning empty result with parallel ALTER TABLE

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-11-04 18:45:16 Re: get_cast_func syscache utility function
Previous Message Bernd Helmle 2014-11-04 18:23:21 Re: COPY TO returning empty result with parallel ALTER TABLE