Re: WIP/PoC for parallel backup - Mailing list pgsql-hackers

From Asim R P
Subject Re: WIP/PoC for parallel backup
Date
Msg-id CANXE4Tc=YmPC7R+WWd6U8MOc4K2p0J7gM9DTk+LTaH693rphxg@mail.gmail.com
Whole thread Raw
In response to WIP/PoC for parallel backup  (Asif Rehman <asifr.rehman@gmail.com>)
Responses Re: WIP/PoC for parallel backup
Re: WIP/PoC for parallel backup
List pgsql-hackers
Hi Asif

Interesting proposal.  Bulk of the work in a backup is transferring files from source data directory to destination.  Your patch is breaking this task down in multiple sets of files and transferring each set in parallel.  This seems correct, however, your patch is also creating a new process to handle each set.  Is that necessary?  I think we should try to achieve this using multiple asynchronous libpq connections from a single basebackup process.  That is to use PQconnectStartParams() interface instead of PQconnectdbParams(), wich is currently used by basebackup.  On the server side, it may still result in multiple backend processes per connection, and an attempt should be made to avoid that as well, but it seems complicated.

What do you think?

Asim

pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: io_uring support
Next
From: Konstantin Knizhnik
Date:
Subject: Re: Why overhead of SPI is so large?