From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
Cc: | Emanuel <postgres(dot)arg(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #6041: Unlogged table was created bad in slave node |
Date: | 2011-05-26 16:24:57 |
Message-ID: | 1306427067-sup-7622@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Excerpts from Euler Taveira de Oliveira's message of jue may 26 12:00:05 -0400 2011:
> 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".
I guess what it should do is create an empty file in the slave.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-05-26 16:34:34 | Re: BUG #6041: Unlogged table was created bad in slave node |
Previous Message | Euler Taveira de Oliveira | 2011-05-26 16:00:05 | Re: BUG #6041: Unlogged table was created bad in slave node |
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 2011-05-26 16:28:08 | Re: LOCK DATABASE |
Previous Message | Tom Lane | 2011-05-26 16:23:02 | Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum |