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

From: Marc Munro <marc(at)bloodnok(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #11867: Strange behaviour with composite types after resetting database tablespace
Date: 2014-11-04 16:14:00
Message-ID: 1415117640.32454.8.camel@bloodnok.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Mon, 2014-11-03 at 22:08 -0500, Tom Lane wrote:
> <spock>Fascinating.</spock>

:-)

> I believe what is happening is:

[ . . . ]

> > This is not mission-critical for me but I'd be grateful for suggestions for
> > work-arounds.
>
> I don't see any workaround that's much easier than fixing the bug.
> But what's your use case that involves flipping databases from one
> tablespace to another and then back again within the life expectancy of
> unused shared-buffers pages? It doesn't seem terribly surprising that
> nobody noticed this before ...

It's a completely unreal use case. I am working on a diff tool, and
this was found as part of my test suite: build db x, drop db x, build
db y, apply diff y->x, compare with original x, apply diff x->y, compare
with original y.

So this is a fairly minor inconvenience for me.

__
Marc

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-11-04 16:45:51 Re: BUG #11867: Strange behaviour with composite types after resetting database tablespace
Previous Message Tom Lane 2014-11-04 03:08:04 Re: BUG #11867: Strange behaviour with composite types after resetting database tablespace

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2014-11-04 16:22:03 Re: alter user set local_preload_libraries.
Previous Message Tom Lane 2014-11-04 15:33:38 Re: Let's drop two obsolete features which are bear-traps for novices