On Saturday, July 31, 2021, Ayub M wrote:
> But when default_statistics_target is increased to 3000, the session usage
> is 463mb
>
IIUC, the analyze process doesn’t consult maintenance_work_mem. It simply
creates an array, in memory, to hold the random sample of rows needed for
computing the r
Hello, when maintenance_work_mem and autovacuum_work_mem are set, my
understanding is that the vacuum and autovacuum sessions should be limited
to use the memory limits set by these parameters. But I am seeing more
memory being used than these limits by autovacuum sessions, any reason why
this woul
=?utf-8?Q?Fran=C3=A7ois_Beausoleil?= writes:
> While mowing the lawn, I thought that since the syntax of multi ranges is
> similar to arrays, maybe I could use unnest(), but sadly, that was not to be
> the case:
> # select
> unnest('{[2021-08-02,2021-08-04],[2021-08-07,2021-08-09)}'::tsmultiran
On 7/31/21 5:16 PM, François Beausoleil wrote:
Hello Adrian,
Yes, in fact, I wrote the following:
--
CREATE FUNCTION generate_series(tstzrange, interval) RETURNS SETOF
ti
Hello Adrian,
> Le 31 juill. 2021 à 15:49, Adrian Klaver a écrit :
>
> On 7/31/21 11:59 AM, François Beausoleil wrote:
>> Hello all!
>> I’m excited for multi ranges, as they fit nicely into a scheduling app. What
>> I’m trying to express is something along the lines of « Every weekday from
>>
On 7/31/21 11:59 AM, François Beausoleil wrote:
Hello all!
I’m excited for multi ranges, as they fit nicely into a scheduling app. What
I’m trying to express is something along the lines of « Every weekday from
2021-08-01 and 2021-10-01, from 9 AM to 8 PM, every 90 minutes ». You can think
of
Hello all!
I’m excited for multi ranges, as they fit nicely into a scheduling app. What
I’m trying to express is something along the lines of « Every weekday from
2021-08-01 and 2021-10-01, from 9 AM to 8 PM, every 90 minutes ». You can think
of public transit for the model.
Initially, I was g
