Re: pg_dumpall with individual output files per database?

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Luca Ferrari <fluca1978(at)gmail(dot)com>
Cc: Francisco Olarte <folarte(at)peoplecall(dot)com>, Thorsten Schöning <tschoening(at)am-soft(dot)de>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_dumpall with individual output files per database?
Date: 2021-07-23 11:04:39
Message-ID: CAECtzeWVW51RYTFx0b98r0Ha3h_aU0MRQe891cFZoYB0kng1-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Le ven. 23 juil. 2021 à 12:06, Luca Ferrari <fluca1978(at)gmail(dot)com> a écrit :

> On Thu, Jul 15, 2021 at 7:27 PM Francisco Olarte <folarte(at)peoplecall(dot)com>
> wrote:
> > It would probably complicate it, and dumping a whole cluster using
> > something like pg_dumpall -g for the globals plus a loop over the
> > databases using something like pg_dump -Fc ( which I would always
> > recommend over plain sql format ) is just a ( little complex ) one
> > liner or a 10 line script, probably not worth the scarce developer /
> > maintainer brain cycles.
>
> I always find the 502.pgsql FreeBSD backup script illuminating in this
> sense: <
> https://svnweb.freebsd.org/ports/head/databases/postgresql10-server/files/502.pgsql.in?view=markup#l44
> >.
> I used it as a base for my "loop and backup" scripts.
>
>
I like the simple pg_back tool ( https://github.com/orgrim/pg_back ). I
much prefer the bash version, but both (bash 1.x version, and go 2.x
version) are working great.

--
Guillaume.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message WR 2021-07-23 11:55:09 Re: Obsolete or dead serverconnections after reboot
Previous Message Luca Ferrari 2021-07-23 10:11:15 Re: dealing with dependencies