Re: Getting rid of postgres output
От | Jim Nasby |
---|---|
Тема | Re: Getting rid of postgres output |
Дата | |
Msg-id | EFDEA163-DD55-4398-85F6-B60E5A2EE2F4@pervasive.com обсуждение исходный текст |
Ответ на | Getting rid of postgres output ("Nicola Mauri" <Nicola.Mauri@saga.it>) |
Список | pgsql-admin |
First, you need to upgrade to 8.1.4. You can redirect STDOUT to /dev/null. Error messages will be sent to STDERR. On Aug 7, 2006, at 9:00 AM, 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. > > Does anyone know how to get rid of this output? > Simply redirecting output is not a great idea, as we may loose some > precious error messages too; so I think we should prevent this > messages to being generate at all. > (Postgres 8.1.3 on RHEL4) > > Thank You! > Nicola > -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
В списке pgsql-admin по дате отправления: