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

From Philip Warner
Subject Re: reproducable command sequence to get "mdopen: Couldn't open..."
Date
Msg-id 3.0.5.32.20001016124800.02924100@mail.rhyme.com.au
Whole thread Raw
In response to Re: reproducable command sequence to get "mdopen: Couldn't open..."  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: reproducable command sequence to get "mdopen: Couldn't open..."
List pgsql-bugs
At 21:41 15/10/00 -0400, Tom Lane wrote:
>Philip Warner <pjw@rhyme.com.au> writes:
>>     NOTICE:  Caution: beyond this point, a mis-spelled attribute name will
>> corrupt your database
>
>How many distinct kinds of typos do you think the message should
>mention?  I'd think something like that would be more confusing
>than not, since it implies that only some kinds of errors are bad.

Er...it was a joke.


>Personally, I'd vote for disallowing ALTER RENAME inside transaction
>blocks until we can do it safely.

I agree totally. The bogus error message was to highlight the fragility of
allowing rename in TX blocks.



----------------------------------------------------------------
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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: reproducable command sequence to get "mdopen: Couldn't open..."
Next
From: Tom Lane
Date:
Subject: Re: reproducable command sequence to get "mdopen: Couldn't open..."