2011/5/26 Euler Taveira de Oliveira <eu...@timbira.com>: > Em 26-05-2011 08:37, Emanuel escreveu: > >> Description: Unlogged table was created bad in 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=# select * from voidy ; >> ERROR: could not open file "base/12071/17034": No existe el archivo 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). -- -- Emanuel Calvo Helpame.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
