Re: [Safekeep-devel] Proposal: removal of '-C' pg_dump option

[Frank C. <fr...@cr...>]

Marco, Dimi,

What was the final decision here?  While we talked about an option, I'm
not sure if we agreed to it in the end, and if it was only limited to
postgres?

Regards
Frank

On Tue, 2014-10-21 at 15:45 +0200, Marco Bozzolan wrote:
> * Dimi Paun <di...@la...> [2014 10 21, 08:33]:
> > As an aside: if no database is specified, it means "dump all" and unless 
> > you have exactly one, it just doesn't make sense not to have a CREATE 
> > DATABASE.
> 
>   This has been my first thought as well, but actually the dump could 
> just contain a  "\connect <dbname>" or a "USE <dbname>" for each 
> database. This could be useful in a situation where you have the 
> databases created by an external script which can perform additional 
> operations (i.e. setting default privileges).
> 
> > For the rest, you've already worked out the right switches, no?
> 
>   It would seem so, but I think that what was really noticeable was the 
> complexity required in order to apply this attribute to every 
> (present, maybe future?) database-dumping tool. In my opinion 
> correcting this behaviour only for PostgreSQL and letting the user 
> customize it for every other tool would just be simpler and more easily 
> extended in future (i.e. there will be no need to find out other 
> switches or to add other warnings when adding support for the next 
> tool).
> 
> Regards,
>