At Tue, 23 Nov 2021 11:21:05 -0300, Alvaro Herrera
wrote in
> On 2021-Nov-22, PG Doc comments form wrote:
>
> > The unit (I assume it's MB) of max_slot_wal_keep_size is not explicitly
> > specified in the docs. If it's intentional then please, disregards, but I've
> > not been able to deduct th
On 11/23/21 12:44 PM, Tom Lane wrote:
Peter Eisentraut writes:
On 23.11.21 07:18, Maciek Sakrejda wrote:
An example in the materialized view documentation [1] includes an ORDER
BY clause without a clear reason. Does it help build the index more
efficiently? I suppose it's also sort of like a C
Peter Eisentraut writes:
> On 23.11.21 07:18, Maciek Sakrejda wrote:
>> An example in the materialized view documentation [1] includes an ORDER
>> BY clause without a clear reason. Does it help build the index more
>> efficiently? I suppose it's also sort of like a CLUSTER?
> I agree the ORDER
On 23.11.21 07:18, Maciek Sakrejda wrote:
An example in the materialized view documentation [1] includes an ORDER
BY clause without a clear reason. Does it help build the index more
efficiently? I suppose it's also sort of like a CLUSTER?
But it seems like the ORDER BY should either be explain
On 2021-Nov-22, PG Doc comments form wrote:
> The unit (I assume it's MB) of max_slot_wal_keep_size is not explicitly
> specified in the docs. If it's intentional then please, disregards, but I've
> not been able to deduct that from this page alone. Thanks!
Well, that's embarrasing. I'll see abo
On Mon, 2021-11-22 at 21:02 +0100, Laurenz Albe wrote:
> On Mon, 2021-11-22 at 19:54 +0100, Max Ziermann wrote:
> > Am 22.11.21 um 16:41 schrieb Laurenz Albe:
> > > On Mon, 2021-11-22 at 12:06 +, PG Doc comments form wrote:
> > > > "Note that the user performing the insert, update or delete on
