Re: [GENERAL] Re: Restoring tables with circular references dumped toseparate files - Mailing list pgsql-general

From Melvin Davidson
Subject Re: [GENERAL] Re: Restoring tables with circular references dumped toseparate files
Date
Msg-id CANu8FizKLjf=KBEaSc-_qEryNM9enp3xJj3S3N1T6pCNJogzjA@mail.gmail.com
Whole thread Raw
In response to [GENERAL] Re: Restoring tables with circular references dumped to separatefiles  (doganmeh <mehmet@edgle.com>)
List pgsql-general


On Sat, Oct 21, 2017 at 4:48 PM, doganmeh <mehmet@edgle.com> wrote:
The list approach for partial restore is also useful, thank you.

On another note, I used to take full backups (entire database), however
switched to table by table scheme in order to make it more VCS friendly.
Namely, so I only check into github the dumps of the tables that are updated
only.

So, from that perspective, is there a dump-restore scenario that is widely
used, but is also VCS friendly? To my knowledge, pg_restore does not restore
backups that are in "plain text" format, and compressed formats such as
"tar" would not be github friendly.



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


>...is there a dump-restore scenario that is widely used, but is also VCS friendly?

You might want to give consideration to pg_extractor.



--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-general by date:

Previous
From: doganmeh
Date:
Subject: [GENERAL] Re: Restoring tables with circular references dumped to separatefiles
Next
From: "Igal @ Lucee.org"
Date:
Subject: Re: [GENERAL] tgrm index for word_similarity