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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: reproducable command sequence to get "mdopen: Couldn't open..."
Дата
Msg-id 5032.971628115@sss.pgh.pa.us
обсуждение исходный текст
Ответ на reproducable command sequence to get "mdopen: Couldn't open..."  (Palle Girgensohn <girgen@partitur.se>)
Ответы Re: reproducable command sequence to get "mdopen: Couldn't open..."  (Philip Warner <pjw@rhyme.com.au>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Selects on tables with cidr type primary keys are broken
Следующее
От: pgsql-bugs@postgresql.org
Дата:
Сообщение: INSERT possible without INSERT-permission