ERROR: column "datpath" does not exist
Hi,
Whenever I try to pg_dump -i my database from the bash, i receive the
following error.
pg_dump: server version: pg_dump.mo; pg_dump version: 7.3.10-RH
pg_dump: proceeding despite version mismatch
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: column "datpath" does not exist
pg_dump: The command was: select (select usename from pg_user where usesysid
= datdba) as dba, encoding, datpath from pg_database where datname = 'mpv'
What's that "datpath" about? Is it a version problem? postgres (PostgreSQL)
7.3.10-RH
Thanks in advance,
Sascha
"Sascha Nepper" <sascha.nepper@webattach.de> writes:
What's that "datpath" about? Is it a version problem? postgres (PostgreSQL)
7.3.10-RH
Yes. Your server must be PG 8.0 or 8.1. Using the "-i" switch to
override pg_dump's version check is hardly ever a good idea --- instead,
find a newer version of pg_dump.
regards, tom lane
Yes. Your server must be PG 8.0 or 8.1. Using the "-i" switch to override
pg_dump's version check is hardly ever a good idea --- instead, find a newer
version of pg_dump.
Sorry, my mistake.
Actually I am using PostgreSQL 8.0.3, but pg_dump is 7.3.10-RH !
So, is there a way to get a newer version of pg_dump?
I guess that's what could help me out.
Please help.
Sascha
What's that "datpath" about? Is it a version problem? postgres (PostgreSQL)
7.3.10-RH
Just set up a new postgres on another server. Restoring my dump and then
trying pg_dump again.
Here's the result:
pg_dump mpv
pg_dump: server version: PostgreSQL 8.1.3 on i686-pc-linux-gnu, compiled by
GCC gcc (GCC) 3.3.1 (SuSE Linux); pg_dump version: 7.3.9
pg_dump: aborting because of version mismatch (Use the -i option to proceed
anyway.)
pg_dump mpv -i
pg_dump: server version: PostgreSQL 8.1.3 on i686-pc-linux-gnu, compiled by
GCC gcc (GCC) 3.3.1 (SuSE Linux); pg_dump version: 7.3.9
pg_dump: proceeding despite version mismatch
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: column "datpath" does not exist
pg_dump: The command was: select (select usename from pg_user where usesysid
= datdba) as dba, encoding, datpath from pg_database where datname = 'mpv'
I cannot understand why this "datpath"-thing happens again... :o(
Regards,
Sascha
On Fri, 2006-03-03 at 10:38, Sascha Nepper wrote:
What's that "datpath" about? Is it a version problem? postgres (PostgreSQL)
7.3.10-RH
Just set up a new postgres on another server. Restoring my dump and then
trying pg_dump again.Here's the result:
pg_dump mpv
pg_dump: server version: PostgreSQL 8.1.3 on i686-pc-linux-gnu, compiled by
GCC gcc (GCC) 3.3.1 (SuSE Linux); pg_dump version: 7.3.9
pg_dump: aborting because of version mismatch (Use the -i option to proceed
anyway.)pg_dump mpv -i
pg_dump: server version: PostgreSQL 8.1.3 on i686-pc-linux-gnu, compiled by
GCC gcc (GCC) 3.3.1 (SuSE Linux); pg_dump version: 7.3.9
pg_dump: proceeding despite version mismatch
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: column "datpath" does not exist
pg_dump: The command was: select (select usename from pg_user where usesysid
= datdba) as dba, encoding, datpath from pg_database where datname = 'mpv'I cannot understand why this "datpath"-thing happens again... :o(
It's simple. Under 8.1.3 something was added to the database that the
new 8.1.3 pg_dump knows about that the 7.3.9 pg_dump couldn't know
about, because it was written a couple years before that had been added
to postgresql, in 8.x (whatever version).
It's quite reasonable to use a newer (i.e. higher version number)
version of pg_dump on an older database, because it's fairly easy to
incorporate backwards compatibility into pg_dump.
But without time travel (not temporal database sets, but real, honest,
get in a box and travel backwards in time) it's pretty hard for an older
version of pg_dump to know how to handle future versions of postgresql,
cause they didn't exist when that version of pg_dump was written.
So, the version of pg_dump should be equal to or greater than the
version of the postgresql database you are dumping, got it?
Thanks Scott, now I got it! ;)
I found older copies of pg_dump in "/usr/bin" while the newer were in
"/usr/local/pgsql/bin/".
Beginner's mistake... 8-)
Sascha
Import Notes
Reply to msg id not found: | Resolved by subject fallback
I am facing this problem but i didn't find the solution what mentioned here.
Where are the folders "/usr/bin" and "usr/local/pgsql/bin/"
[webattach] IT-Dienstleistungen wrote:
Thanks Scott, now I got it! ;)
I found older copies of pg_dump in "/usr/bin" while the newer were in
"/usr/local/pgsql/bin/".Beginner's mistake... 8-)
Sascha
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
--
View this message in context: http://www.nabble.com/-GENERAL--ERROR%3A--column-%22datpath%22-does-not-exist-tp3213375p19855174.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
On Tue, Oct 7, 2008 at 4:08 AM, tsp <PRAVEEN@oneindia.in> wrote:
I am facing this problem but i didn't find the solution what mentioned here.
Where are the folders "/usr/bin" and "usr/local/pgsql/bin/"
Then I guess the first question is what OS are you running and how
were the current and previous versions of pgsql installed?