Re: RE : PostgreSQL logical incremental backup for version 9.6 and above

Hi Pascal,
Thanks for the suggestion. Looks like pgBackRest relies on WAL archive
logs. But for Amazon RDS or Azure Database WAL logs are not accessible. We
can only do pg_dump and logical replication.
So pgBackRest won't work for my case.

Thanks
Girish

On Wed, Nov 6, 2019 at 2:05 PM PASCAL CROZET <
pascal(dot)crozet(at)qualis-consulting(dot)com> wrote:

> Hi,
>
>
>
> I think you can user pgBackRest <https://pgbackrest.org/>
>
>
>
> *_________________________________*
>
> Cordialement, *Pascal CROZET*
>
> *DBA - * <http://www.qualis-consulting.com>Qualis Consulting
> <http://www.qualis-consulting.com/>
>
> • www.qualis-consulting.com • 04 78 22 74 90
> • Le Bois des Côtes 1 – Bâtiment A
> • 300 Route Nationale 6 – 69760 LIMONEST
> *_________________________________*
>
>
>
> *De : *girish R G peetle <giri(dot)anamika0(at)gmail(dot)com>
> *Envoyé le :*mercredi 6 novembre 2019 18:03
> *À : *pgsql-admin <pgsql-admin(at)postgresql(dot)org>
> *Objet :*PostgreSQL logical incremental backup for version 9.6 and above
>
>
> Hi,
> I've a requirement to backup incremental data from PostgreSQL database
> server which are hosted as 'database as a service' like 'Amazon RDS' ,
> Azure Database etc.
>
> Full dump can be taken using pg_dump. But is there is a way to capture
> incremental changes to the database ? I read about logical replication
> slots which can be created for each database to capture incremental
> changes.
> But how do we know from where we should backup the SQL statements (as we
> need need skip those statements already backed up by pg_dump).
>
> I thinking of following steps.
> Step 1: Create logical replication slot
> Step 2: Run pg_dump ( for full load ).
> Step 3: Capture the changes since last pg_dump using replication slot -
> How to know this information ?
>
> Thanks in advance for any advise.
>
> Thanks
> Girish
>