Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
When you built postgres from source. PG_DUMP is in /usr/local/pgsql/bin/pg_dump or anywhere you've been setting in --prefix. Be aware, /usr/bin/pg_dump can contain different version, that has been installed with your system.
If 'pg_dump --version' doesn't show anything then something is really wrong.
The error messages suggest that pg_dump is a script (and they are not bash error messages).
What is pg_dump? On Debian Squeeze it is symlinked to a Perl script:
docoll@CW8vDS:~$ type pg_dump
pg_dump is /usr/bin/pg_dump
docoll@CW8vDS:~$ file /usr/bin/pg_dump
/usr/bin/pg_dump: symbolic link to `../share/postgresql-common/pg_wrapper'
docoll@CW8vDS:~$ file /usr/share/postgresql-common/pg_wrapper
/usr/share/postgresql-common/pg_wrapper: a /usr/bin/perl -w script text executable
Sorry to confuse. The bash type builtin command and the file binary command can be used as shown at the command prompt to determine what is run in response to using a particular command at the command prompt.
I did not know it was possible to run pg_dump from within an interactive PostgreSQL session. Maybe it's not and hence the error message.
What happens if you try running it at the command prompt?