That worked!!! Thanks!!!
I have one last problem.
It works correctly at the command line:
postgres ~
$ ./pg_backup.sh
User: postgres
PWD: /Library/PostgreSQL/9.3
HOME: /Library/PostgreSQL/9.3
BACKUP_DIR: /Users/backup/postgres/
BACKUP_DIR_DATED: /Users/backup/postgres/2013-11-21/
----- Full backups Begin -----
Backing up postgres ---> /Users/backup/postgres/2013-11-21/postgres.sql.gz
Backing up rincon ---> /Users/backup/postgres/2013-11-21/rincon.sql.gz
----- Full backups End -----
When I run it as a job in postgres, it fails. Here are the results:
662 Failed 1 Thu Nov 21 19:02:38 2013 Thu Nov 21 19:02:38 2013
00:00:00.016344
User: postgres
PWD: /Library/PostgreSQL/9.3
HOME: /Library/PostgreSQL/9.3
BACKUP_DIR: /Users/backup/postgres/
BACKUP_DIR_DATED: /Users/backup/postgres/2013-11-21/
----- Full backups Begin -----
No schemas returned from database. This could be a password issue.
It is behaving like it could not login to get the schema list.
Since prompting for a password is not an error message, it is not displayed
in the error log.
How can I debug this job?
Thanks,
Pat
On Thu, Nov 21, 2013 at 5:36 PM, Euler Taveira <euler@timbira.com.br> wrote:
> On 21-11-2013 18:06, Patrick Lademan wrote:
> > I have changed the permissions and run it as user postgres.
> > This time, it prompted for a password on the 2nd time through the loop.
> >
> That's because the database is 'postgres' in your password file. Try:
>
> localhost:5432:*:postgres:XXXXXX
>
>
> --
> Euler Taveira Timbira - http://www.timbira.com.br/
> PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
>