From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
---|---|
To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
Cc: | 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 10:05:19 |
Message-ID: | CAKoxK+5wGAyXMUEZ=kFrg8_s8FBqSn6uBXR_xstSSp-TE-EWqg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Luca
From | Date | Subject | |
---|---|---|---|
Next Message | Luca Ferrari | 2021-07-23 10:11:15 | Re: dealing with dependencies |
Previous Message | Luca Ferrari | 2021-07-23 09:47:57 | Re: PostgreSQL 9.2 high replication lag |