On 2020/04/28 13:37, Michael Paquier wrote:
On Mon, Apr 27, 2020 at 12:16:41PM +0200, Daniel Gustafsson wrote:
Based on a recent conversation about backups I had I propose a small tweak to
the pg_basebackup documentation. Listing the user types in the reverse order
from today, putting superu
On Mon, Apr 27, 2020 at 12:16:41PM +0200, Daniel Gustafsson wrote:
> Based on a recent conversation about backups I had I propose a small tweak to
> the pg_basebackup documentation. Listing the user types in the reverse order
> from today, putting superuser last, makes it IMO a little clearer that
On Mon, Apr 27, 2020 at 07:24:45PM +0300, Олег Самойлов
wrote:
> Yes, I saw recommendations for 1.1 early, but why? Why such exactly
> precision number, why 1.1? Is here ever a theoretical or experimental
> prof?
Well, SSD random performance is slightly slower than sequential, so the
value should
Yes, I saw recommendations for 1.1 early, but why? Why such exactly precision
number, why 1.1? Is here ever a theoretical or experimental prof?
As for me, random_page_cost depended not only not characteristic of a storage
device (hdd or ssd), but also on assumptions about how much of the databas
Alexander Lakhin writes:
> 27.04.2020 18:04, Tom Lane wrote:
>> BTW, I tried to also use this markup inside the template for
>> , so we'd only need one font-switching special case not two.
>> Didn't work though --- apparently templates don't get applied recursively?
> We can have a single templa
On Mon, Apr 27, 2020 at 06:02:41AM +0200, Pavel Stehule wrote:
>
>
> ne 26. 4. 2020 v 21:25 odesílatel yigong hu napsal:
>
> Sorry to hijack the thread, I also recently have similar observation that
> the statement about random_page_cost on SSD is ambiguous. The current
> document s
27.04.2020 18:04, Tom Lane wrote:
> Alexander Lakhin writes:
>> 26.04.2020 22:13, Tom Lane wrote:
>> BTW, I tried to also use this markup inside the template for
>> , so we'd only need one font-switching special case not two.
>> Didn't work though --- apparently templates don't get applied recurs
Alexander Lakhin writes:
> 26.04.2020 22:13, Tom Lane wrote:
>> Use of a new processing-instruction might not be the most elegant
>> way to do this ... anyone have a better suggestion?
> I would use the phrase tag, which is intended for such uses: [1] [2].
Good idea, done that way.
> The "phras
Based on a recent conversation about backups I had I propose a small tweak to
the pg_basebackup documentation. Listing the user types in the reverse order
from today, putting superuser last, makes it IMO a little clearer that a
REPLICATION role is preferrable to using a superuser for running backu
