Re: reproducable command sequence to get "mdopen: Couldn't open..." - Mailing list pgsql-bugs

From Tom Lane
Subject Re: reproducable command sequence to get "mdopen: Couldn't open..."
Date
Msg-id 5032.971628115@sss.pgh.pa.us
Whole thread Raw
In response to reproducable command sequence to get "mdopen: Couldn't open..."  (Palle Girgensohn <girgen@partitur.se>)
Responses Re: reproducable command sequence to get "mdopen: Couldn't open..."
List pgsql-bugs
Palle Girgensohn <girgen@partitur.se> writes:
> BEGIN;
> BEGIN
> ALTER TABLE at_provider_user_info RENAME TO tmp;
> NOTICE:  Caution: RENAME TABLE cannot be rolled back, so don't abort now
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ followed by deliberately-provoked error to abort the transaction ]

Well, it did tell you not to do this ;-)

Making ALTER TABLE RENAME abort-safe requires changing the conventions
for naming physical table files, and the details have been sufficiently
controversial that it's not been done yet.  In the meantime our only
choices are to forbid ALTER TABLE RENAME within transaction blocks, or
allow it with the knowledge that people can shoot themselves in the foot
with it.  The above warning notice is the current compromise.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Selects on tables with cidr type primary keys are broken
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: INSERT possible without INSERT-permission