Re: Changing pg_dump default file format

On 11/07/2013 10:54 AM, Kevin Grittner wrote:

> That is who I am thinking of.  A DBA team may have hundreds of
> databases to manage, each with many scripts which have been running
> nicely for years.  A change like this is bound to break some of
> those crontab scripts they may not even remember they are running
> -- like ones which dump a key table to INSERT statements to feed
> into some other database product, which will now choke when it gets
> a custom format file instead of the text file it has been getting
> for years.  Requiring the DBA team to track all these scripts down
> to add -Fp would be annoying, to put it mildly.

Only because they don't take the time to properly document or put into 
some form of automation/tracking/configfile management mechanism.

Don't get me wrong, I would be in the same boat but I don't think it is 
realistic to manage the communities expectations with the lackluster 
operations performance of fellow DBAs.

JD

-- 
Command Prompt, Inc. - http://www.commandprompt.com/  509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms   a rose in the deeps of my heart. - W.B. Yeats