Greetings,
* Fabio Pardi (f.pa...@portavita.eu) wrote:
> I understand that in this thread we are contextualizing in a step by
> step procedure to create a new standby, but I have anyway a few remarks
> about it (and the documentation where it has been copied from) and I
> would be glad if you or s
Greetings,
* Bruce Momjian (br...@momjian.us) wrote:
> On Fri, Jun 14, 2019 at 10:39:40AM -0400, Bruce Momjian wrote:
> > On Fri, Jun 14, 2019 at 03:12:29PM +0200, Fabio Pardi wrote:
> > > Using --size-only, tells rsync to only check the size of the blocks.
> > > That is: if the block is present o
On Fri, Jun 14, 2019 at 10:39:40AM -0400, Bruce Momjian wrote:
> On Fri, Jun 14, 2019 at 03:12:29PM +0200, Fabio Pardi wrote:
> > Using --size-only, tells rsync to only check the size of the blocks.
> > That is: if the block is present on the destination, and is the same
> > size as the origin, the
On Fri, Jun 14, 2019 at 03:12:29PM +0200, Fabio Pardi wrote:
> Hi Bruce,
>
>
> On 6/14/19 5:30 AM, Bruce Momjian wrote:
>
> >> Also, I do not think it best practice (or perhaps not correct at all) to
> >> use '--size-only'
> >
> > --size-only is correct, as far as I know.
> >
>
>
> Maybe I a
Hi,
Maybe of some interest for the past, present and future community, I
benchmarked the impact of wal_log_hints with and without wal_compression
enabled.
https://portavita.github.io/2019-06-14-blog_PostgreSQL_wal_log_hints_benchmarked/
comments are welcome.
regards,
fabio pardi
Hi Bruce,
On 6/14/19 5:30 AM, Bruce Momjian wrote:
>> Also, I do not think it best practice (or perhaps not correct at all) to
>> use '--size-only'
>
> --size-only is correct, as far as I know.
>
Maybe I am missing something, but I am of the opinion that --size-only
should not be used when s
