Re: 20220221-Clarification regarding PostgeSQL DB backup

2022-02-20 Thread Daevor The Devoted
Monday, February 21, 2022 11:05 AM > *To:* Techsupport > *Cc:* pgsql-generallists.postgresql.org > *Subject:* Re: 20220221-Clarification regarding PostgeSQL DB backup > > > > Hi Karthick > > > > I'm a little rusty on PG (it's been about a decade since I l

RE: 20220221-Clarification regarding PostgeSQL DB backup

2022-02-20 Thread Techsupport
: Daevor The Devoted [mailto:doll...@gmail.com] Sent: Monday, February 21, 2022 11:05 AM To: Techsupport Cc: pgsql-generallists.postgresql.org Subject: Re: 20220221-Clarification regarding PostgeSQL DB backup Hi Karthick I'm a little rusty on PG (it's been about a decade since I l

Re: 20220221-Clarification regarding PostgeSQL DB backup

2022-02-20 Thread Ron
On 2/20/22 10:59 PM, Techsupport wrote: Hi Team, ** We have used PG_DUMP to take backup of particular database from the PostgreSQL Server. It takes too long to restore the databases , which has  Half Billion records (almost 8 Hour) My primary need is to make the Differential and Incremental

Re: 20220221-Clarification regarding PostgeSQL DB backup

2022-02-20 Thread Daevor The Devoted
Hi Karthick I'm a little rusty on PG (it's been about a decade since I last worked intensely with it), but I seem to remember that restoring with indexes can be very slow. The faster approach is to restore *without* indexes, and then create the indexes once the data restore is complete. My knowle

20220221-Clarification regarding PostgeSQL DB backup

2022-02-20 Thread Techsupport
Hi Team, We have used PG_DUMP to take backup of particular database from the PostgreSQL Server. It takes too long to restore the databases , which has Half Billion records (almost 8 Hour) My primary need is to make the Differential and Incremental backup on the Windows Serv