Re: reproducable command sequence to get "mdopen: Couldn't open..."

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Palle Girgensohn <girgen(at)partitur(dot)se>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: reproducable command sequence to get "mdopen: Couldn't open..."
Date: 2000-10-15 16:41:55
Message-ID: 5032.971628115@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Palle Girgensohn <girgen(at)partitur(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2000-10-15 19:17:39 INSERT possible without INSERT-permission
Previous Message Tom Lane 2000-10-15 16:30:19 Re: Selects on tables with cidr type primary keys are broken