Skip site navigation (1) Skip section navigation (2)

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

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Palle Girgensohn <girgen(at)partitur(dot)se>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: reproducable command sequence to get "mdopen: Couldn't open..."
Date: 2000-10-16 02:48:00
Message-ID: 3.0.5.32.20001016124800.02924100@mail.rhyme.com.au (view raw or flat)
Thread:
Lists: pgsql-bugs
At 21:41 15/10/00 -0400, Tom Lane wrote:
>Philip Warner <pjw(at)rhyme(dot)com(dot)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   |/

In response to

Responses

pgsql-bugs by date

Next:From: Mikheev, VadimDate: 2000-10-16 07:50:42
Subject: Ответ: [BUGS] reproducable command ?==?koi8-r?Q?sequence to get "mdopen: Couldn't open..."
Previous:From: Philip WarnerDate: 2000-10-16 02:35:19
Subject: Re: reproducable command sequence to get "mdopen: Couldn't open..."

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group