>
> Hm ... there was a fix in 9.0.12 that might be relevant to this:
>
> http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=5840e3181b7e6c784fdb3aff708c4dcc2dfe551d
> Whether that explains it or not, 9.0.5 is getting long in the tooth;
> you really need to think about an update. Esp
Dale Fukami writes:
> On Tue, Apr 16, 2013 at 3:04 PM, Tom Lane wrote:
>> Either way, if it's working on the master, then you've had a replication
>> failure since the standby's files evidently don't match the master's.
>>
>> What PG version is this (and which versions have been installed since
On Tue, Apr 16, 2013 at 3:04 PM, Tom Lane wrote:
> Dale Fukami writes:
> > I'm having a problem on a standby server (streaming replication) where a
> > table seems to exist but is not queryable. Essentially a select statement
> > (and drop/insert/etc) fails but \d and pg_tables show it exists. T
Dale Fukami writes:
> I'm having a problem on a standby server (streaming replication) where a
> table seems to exist but is not queryable. Essentially a select statement
> (and drop/insert/etc) fails but \d and pg_tables show it exists. The table
> exists on the master (and is queryable) and repl
On 4/16/2013 1:48 PM, Dale Fukami wrote:
Tried the select with the quotes around each of the schema and table
and I get the same result ("someschema"."tracked_deductibles"). I'm
pretty certain they're both lowercase. Would the select from pg_tables
show if they were mixed case by accident?
Tried the select with the quotes around each of the schema and table and I
get the same result ("someschema"."tracked_deductibles"). I'm pretty
certain they're both lowercase. Would the select from pg_tables show if
they were mixed case by accident?
Dale
On Tue, Apr 16, 2013 at 2:38 PM, John R Pi
On 4/16/2013 1:29 PM, Dale Fukami wrote:
live=# select * from someschema.tracked_deductibles;
ERROR: relation "someschema.tracked_deductibles" does not exist
LINE 1: select * from someschema.tracked_deductibles;
live=#\d
List of relations
Schema
Hi,
I'm having a problem on a standby server (streaming replication) where a
table seems to exist but is not queryable. Essentially a select statement
(and drop/insert/etc) fails but \d and pg_tables show it exists. The table
exists on the master (and is queryable) and replication is still working
