>>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 withi
Philip Warner <[EMAIL PROTECTED]> writes:
> Er...it was a joke.
My mistake, missed the smiley :-(
>> Personally, I'd vote for disallowing ALTER RENAME inside transaction
>> blocks until we can do it safely.
> I agree totally.
Well, does anyone want to re-open the issue? ALTER TABLE RENAME an
At 21:41 15/10/00 -0400, Tom Lane wrote:
>Philip Warner <[EMAIL PROTECTED]> 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 wo
Philip Warner <[EMAIL PROTECTED]> 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 implie
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 RENAM
Palle Girgensohn <[EMAIL PROTECTED]> 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-provok
Hi!
I have seen this problem on several occasions, using 7.02:
# vacuum;
NOTICE: mdopen: couldn't open at_provider_user_info: No such file or directory
NOTICE: RelationIdBuildRelation: smgropen(at_provider_user_info): No such file or
directory
NOTICE: mdopen: couldn't open at_provider_user_i
