On 11/4/14, 10:45 AM, Tom Lane wrote:
So it's safe as things stand; but this seems a bit, um, rickety. Should
we insert a DropRelFileNodesAllBuffers call into ATExecSetTableSpace to
make it safer? It's kind of annoying to have to scan the buffer pool
twice, but I'm afraid that sometime in the f
I wrote:
> However: at no point in this sequence did we flush the original catalog
> blocks out of shared buffers. Therefore, a read of the database's
> pg_class or pg_type at this point is likely to find the previous states of
> those pages (pre-composite-type-drop) as valid, matching entries, so
m...@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 chan
