| From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
|---|---|
| To: | Emanuel <postgres(dot)arg(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6041: Unlogged table was created bad in slave node |
| Date: | 2011-05-26 16:00:05 |
| Message-ID: | 4DDE7905.6050406@timbira.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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].
> 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".
[1] http://www.postgresql.org/docs/9.1/static/sql-createtable.html
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-05-26 16:24:57 | Re: BUG #6041: Unlogged table was created bad in slave node |
| Previous Message | Emanuel | 2011-05-26 11:37:29 | BUG #6041: Unlogged table was created bad in slave node |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | panam | 2011-05-26 16:08:07 | Re: Hash Anti Join performance degradation |
| Previous Message | Robert Haas | 2011-05-26 15:55:58 | Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum |