On Mon, Oct 06, 2014 at 07:24:32PM +0300, Heikki Linnakangas wrote: > On 10/06/2014 07:00 PM, Gabriele Bartolini wrote: > >Hello, > > > >2014-10-06 17:51 GMT+02:00 Marco Nenciarini <marco.nenciar...@2ndquadrant.it > >>: > > > >>I agree that a full backup does not need to include a profile. > >> > >>I've added the option to require the profile even for a full backup, as > >>it can be useful for backup softwares. We could remove the option and > >>build the profile only during incremental backups, if required. However, > >>I would avoid the needing to scan the whole backup to know the size of > >>the recovered data directory, hence the backup profile. > > > >I really like this approach. > > > >I think we should leave users the ability to ship a profile file even in > >case of full backup (by default disabled). > > I don't see the point of making the profile optional. Why burden the user > with that decision? I'm not convinced we need it at all, but if we're going > to have a profile file, it should always be included.
+1 for fewer user decisions, especially with something light-weight in resource consumption like the profile. Cheers, David. -- David Fetter <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers