On 3/19/21 4:32 AM, Marina Polyakova wrote:
On 2021-03-18 18:04, David Steele wrote:
Seems like there should have been a patch attached?
IMO there's a technical problem with sending, receiving (or displaying
on the site) emails from the list pgsql-hackers. By subsribing to this
list I recei
Hello everyone in this thread!
On 2021-03-18 18:04, David Steele wrote:
Seems like there should have been a patch attached?
IMO there's a technical problem with sending, receiving (or displaying
on the site) emails from the list pgsql-hackers. By subsribing to this
list I received the attach
On 3/18/21 11:37 AM, Andrey Borodin wrote:
18 марта 2021 г., в 20:04, David Steele написал(а):
it would be nice to support an interface that simply says to the restore_command,
"go get 1gb of WAL and write the files here."
+1 to redesigning restore_command and archive_command.
Indeed, ar
> 18 марта 2021 г., в 20:04, David Steele написал(а):
> it would be nice to support an interface that simply says to the
> restore_command, "go get 1gb of WAL and write the files here."
+1 to redesigning restore_command and archive_command.
Best regards, Andrey Borodin.
Hi Dimtry,
On 1/11/21 2:51 AM, Dmitry Shulga wrote:
Hi Stephen
Based on our last discussion I redesigned the implementation of WAL
archive recovery speed-up.
Seems like there should have been a patch attached? In any case the
current patch no longer applies so marked Waiting on Author.
P
Hi StephenBased on our last discussion I redesigned the implementation of WAL archive recovery speed-up. The main idea of the new implementation was partly borrowed from your proposal, to be more accurate from the following one:On 9 Nov 2020, at 23:31, Stephen Frost wrote:The r
On 09.11.2020 19:31, Stephen Frost wrote:
Greetings,
* Dmitry Shulga (d.shu...@postgrespro.ru) wrote:
On 19 Oct 2020, at 23:25, Stephen Frost wrote:
process finishes a WAL file but then just sit around doing nothing while
waiting for the applying process to finish another segment.
I believe
Greetings,
* Dmitry Shulga (d.shu...@postgrespro.ru) wrote:
> > On 19 Oct 2020, at 23:25, Stephen Frost wrote:
> Implementation of this approach assumes running several background
> processes (bgworkers)
> each of which runs a shell command specified by the parameter
> resto
Hello Stephen,
> On 19 Oct 2020, at 23:25, Stephen Frost wrote:
>
> Greetings,
>
Implementation of this approach assumes running several background
processes (bgworkers)
each of which runs a shell command specified by the parameter
restore_command
to deliver an archiv
Greetings,
* Dmitry Shulga (d.shu...@postgrespro.ru) wrote:
> > On 9 Sep 2020, at 21:26, Stephen Frost wrote:
> > * Dmitry Shulga (d.shu...@postgrespro.ru) wrote:
> >> Overall archive file processing is done one by one, and this might
> >> create a performance bottleneck if archived WAL files are
Hello Stephen
> On 9 Sep 2020, at 21:26, Stephen Frost wrote:
>
> Greetings,
>
> * Dmitry Shulga (d.shu...@postgrespro.ru) wrote:
>> Overall archive file processing is done one by one, and this might
>> create a performance bottleneck if archived WAL files are delivered slowly,
>> because the d
Greetings,
* Dmitry Shulga (d.shu...@postgrespro.ru) wrote:
> Overall archive file processing is done one by one, and this might
> create a performance bottleneck if archived WAL files are delivered slowly,
> because the database server has to wait for arrival of the next
> WAL segment before appl
út 8. 9. 2020 v 6:51 odesílatel Dmitry Shulga
napsal:
> Hello hackers,
>
> Currently, database recovery from archive is performed sequentially,
> by reading archived WAL files and applying their records to the database.
>
> Overall archive file processing is done one by one, and this might
> crea
13 matches
Mail list logo