Skip site navigation (1) Skip section navigation (2)

pg_dump warning message

From: David Rickard <David(dot)Rickard(at)GTScompanies(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: pg_dump warning message
Date: 2004-04-12 16:24:01
Message-ID: 5.2.1.1.0.20040412091611.032cd548@mail.gtscompanies.com (view raw or flat)
Thread:
Lists: pgsql-novice
Postgres version: 7.3.4
Environment: Solaris (SunOS 5.9) Ultra-250
We use pg_dump to do a nightly export of all databases, via these commands:

for instance in $(get_instances) ; do
   outfile=${exportdir}/${instance}~EXPORT~${ymd}.sql
   su - ${pg_user} -c "${pg_home}/bin/pg_dump -c -C -D -F c -f ${outfile} 
${instance}"
   gzip ${outfile}
done

The pg_dump switches indicate a "custom" file format, and the output file 
is a standard plain-text UNIX file.
Nevertheless, when the export runs, it throws this warning for each 
database instance:

pg_dump: [archiver] WARNING: requested compression not available in this 
installation - archive will be uncompressed

This does not appear to affect the contents of the export file--but it 
would be nice to understand what is generating these messages--and to 
eliminate the chatter (which the system crontab treats as error messages);


--

David Rickard
Software Engineer
The GTS Companies
A TechBooks Company

---------------------------------------------------------------------------------- 

The GTS Companies:
GTS Publishing Services, GTS Graphics, GTS Innova:
Your Single-Source Solution!
Los Angeles CA  *  York, PA  *  Boston MA  *  New Delhi, India
---------------------------------------------------------------------------------- 



David(dot)Rickard(at)GTSCompanies(dot)com
Visit us on the World Wide Web
http://www.gtscompanies.com
5650 Jillson St., Los Angeles, CA 90040
(323) 888-8889 x331
(323) 888-1849 [fax]

Responses

pgsql-novice by date

Next:From: Tom LaneDate: 2004-04-12 18:36:21
Subject: Re: pg_dump warning message
Previous:From: Manfred KoroschetzDate: 2004-04-11 00:29:15
Subject: Re: Help for MSSQL "Compute" equivalent in Postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group