Re: reproducable command sequence to get "mdopen: Couldn't open..."
От | Philip Warner |
---|---|
Тема | Re: reproducable command sequence to get "mdopen: Couldn't open..." |
Дата | |
Msg-id | 3.0.5.32.20001016123519.01f31150@mail.rhyme.com.au обсуждение исходный текст |
Ответ на | Re: reproducable command sequence to get "mdopen: Couldn't open..." (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: reproducable command sequence to get "mdopen: Couldn't open..."
|
Список | pgsql-bugs |
At 12:41 15/10/00 -0400, Tom Lane wrote: > >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. Is it going to be in 7.1? If not, it might be worth disabling in TX blocks since a mistyped SQL query can cause an aborted transaction, something that is somewhat counter-intuitive. Maybe the message should be expanded to say: NOTICE: Caution: beyond this point, a mis-spelled attribute name will corrupt your database Just an idea... ;-) ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 0500 83 82 82 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/
В списке pgsql-bugs по дате отправления: