Re: Getting rid of postgres output

Поиск
Список
Период
Сортировка
От Scott Marlowe
Тема Re: Getting rid of postgres output
Дата
Msg-id 1155072098.20252.63.camel@state.g2switchworks.com
обсуждение исходный текст
Ответ на Getting rid of postgres output  ("Nicola Mauri" <Nicola.Mauri@saga.it>)
Список pgsql-admin
On Mon, 2006-08-07 at 09:00, Nicola Mauri wrote:
> I scheduled a dump between two databases, via network:
>
> pg_dump --clean -U postgres mydb  | psql -q -h remote_host -d mydb -U
> postgres
>
> I'd like to have no output being generated, unless an error condition
> occurs, so that crond will email me only when something goes really
> wrong.
> Unfortunately I'm getting this output:
>
>  setval
> --------
> 551776
> (1 row)
>
> setval
> --------
> 340537
> (1 row)
>
> setval
> --------
>  10411
> (1 row)
>
> and so on........
> It seems to be related to some sequences recently added to the
> database. Actually we are getting one 'setval' line for each sequence
> defined.

It'll just get worse as your database gets bigger.

What's better is to check the output of the pg_dump / psql command.  If
you're using bash shell, you can do something like:

if ! ( pg_dump --clean -U postgres test > /tmp/pgdump.sql ) ; then
    echo "failure in backup" | mail -s "backup failed" youremailhere;
fi

if ! ( psql test2 < /tmp/pgdump.sql ) ; then
    echo "restore failed" | mail -s "restore failed" youremailhere;
fi

or something like that.  you can save the std out like the other poster
pointed out as well.


В списке pgsql-admin по дате отправления:

Предыдущее
От: Darcy Buskermolen
Дата:
Сообщение: Re: running PostGres without installing it
Следующее
От: Jim Nasby
Дата:
Сообщение: Re: Getting rid of postgres output