From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | pg_dump and pgpool |
Date: | 2004-12-29 21:07:06 |
Message-ID: | 1104354426.5893.12.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I've noticed today that if one tries to pg_dump a database cluster
running under pgpool, one gets the error message:
pg_dump: query to get table columns failed: ERROR: kind mismatch
between backends
HINT: check data consistency between master and secondary
Looking at the SQL that pg_dump sends to be relying on object OIDs for
the dump. Would it be reasonable at some date to design pg_dump to work
by joining whatever query would get the OID with the query that would
use it as where criteria so that the OID itself is never reported?
Would there be any interest in such changes, were they made, making
their way into the backend?
Does my question even make sense? It's been a long couple of weeks...
From | Date | Subject | |
---|---|---|---|
Next Message | Eric Brown | 2004-12-29 21:38:42 | debug_print_plan (pg7.4) doesn't seem to do anything |
Previous Message | Dann Corbit | 2004-12-29 21:01:14 | Re: BCD format |