Re: BUG #6041: Unlogged table was created bad in slave node

2011/5/26 Euler Taveira de Oliveira <euler@timbira.com>:
> Em 26-05-2011 08:37, Emanuel escreveu:
>
>> Description: =C2=A0 =C2=A0 =C2=A0 =C2=A0Unlogged table was created bad i=
n slave node
>>
> Unlogged table contents are not available to slave nodes [1].
>

I know it. But the error raised isn't pretty nice for common users.
IMHO it could be an empty file with a message of WARNING level,
for notify administratros to watch up these tables.

>> postgres=3D# select * from voidy ;
>> ERROR: =C2=A0could not open file "base/12071/17034": No existe el archiv=
o o
>> directorio
>>
> I think we should emit the real cause in those cases, if possible (not too
> much overhead). The message would be "Unlogged table content is not
> available in standby server".
>

I think that detecting if table is unlogged && file not exists, rise
this message.
But the problem will comes when the standby is promoted to master, in that
case I didn't test what happens (file not exists, i think it will
couldn't insert data
directly or may force to the dba drop the table from catalog).


--=20
--
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Emanuel Calvo
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Helpame.com