I would say that's the one thing that rsync is *not*. pg_basebackup takes care of a lot of things under the hood. rsync is a lot more complicated, in particular in failure scenarios, since you have to manually deal with pg_start/stop_backup().
There are definitely reasons you'd prefer rsync over pg_basebackup, but I don't believe simplicity is one of them. //Magnus On Tue, Mar 25, 2014 at 4:18 PM, Ilya Kosmodemiansky < ilya.kosmodemian...@postgresql-consulting.com> wrote: > Joshua, > > that is really good point: an alternative is to use pg_basebackup > through ssh tunnel with compression, but rsync is much simpler. > > On Tue, Mar 25, 2014 at 3:56 PM, Joshua D. Drake <j...@commandprompt.com> > wrote: > > > > On 03/25/2014 05:05 AM, Claudio Freire wrote: > >> > >> > >> On Tue, Mar 25, 2014 at 4:39 AM, David Johnston <pol...@yahoo.com> > wrote: > >>>> > >>>> Hai, > >>>> > >>>> Can anyone tell me the difference and performance between pgdump and > >>>> pg_basebackup if I want to backup a large database. > >>>> > > > > Honestly, > > > > Neither is particularly good at backing up large databases. I would look > > into PITR with rsync. > > > > 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 > > Political Correctness is for cowards. > > > > > > > > -- > > Sent via pgsql-performance mailing list ( > pgsql-performance@postgresql.org) > > To make changes to your subscription: > > http://www.postgresql.org/mailpref/pgsql-performance > > > > -- > Ilya Kosmodemiansky, > > PostgreSQL-Consulting.com > tel. +14084142500 > cell. +4915144336040 > i...@postgresql-consulting.com > > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/