From: | Muhammad Ikram <mmikram(at)gmail(dot)com> |
---|---|
To: | Gayatri Singh <gayatripremselvi(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, pgsql-hackers Owner <pgsql-hackers-owner(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Backup and Restore of Partitioned Table in PG-15 |
Date: | 2024-06-16 11:59:55 |
Message-ID: | CAGeimVr6SEoQf7VrL9kZM-hW91PiOMyF+pda6cY5R3Nny+XFcQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Gayatri Singh,
Could you try pgBackRest ?
Its advantages are speed, support for incremental backups, minimal
locking, and robust point in time recovery options besides several advanced
features.
Best suites for large-scale and critical PostgreSQL deployments.
Regards,
Muhammad Ikram
Bitnine Global
On Sun, Jun 16, 2024 at 4:09 AM Gayatri Singh <gayatripremselvi(at)gmail(dot)com>
wrote:
> Hi Team,
>
> Greetings of the day!!
>
> We are planning to partition tables using pg_partman. Like we are planning
> for their backup and restoration process.
>
> Got a few URLs where pg_dump had issues while restoring some data that was
> lost.
>
> kindly guide me the process or steps I need to follow for backing up
> partitioned tables correctly so that while restoration I don't face any
> issue.
>
> Another question, currently we are using pg_dump for database backup which
> locks tables and completely puts db transactions on hold. For this I want
> tables shouldnt get locked also the backup process should complete in less
> time.
>
> Thanks in advance!!
>
> Thanks & Regards,
> Gayatri
>
>
>
--
Muhammad Ikram
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2024-06-16 14:07:08 | Re: race condition in pg_class |
Previous Message | Tatsuo Ishii | 2024-06-16 07:38:46 | Re: create role manual |