Il giorno dom 14 lug 2019 alle ore 22:23 Tom Lane ha
scritto:
> [ please do not top-post in your replies, it makes the conversation hard
> to follow ]
>
> Nicola Contu writes:
> > Il dom 14 lug 2019, 21:34 Kaixi Luo ha scritto:
> >> This is normal and something to be expected. When refreshing
[ please do not top-post in your replies, it makes the conversation hard
to follow ]
Nicola Contu writes:
> Il dom 14 lug 2019, 21:34 Kaixi Luo ha scritto:
>> This is normal and something to be expected. When refreshing the
>> materialized view, the new data is written to a disk and then the t
It does not. That's the issue.
It always increases of 120mb and it reached 12gb instead of just 180mb.
Il dom 14 lug 2019, 21:34 Kaixi Luo ha scritto:
>
> On Fri, Jul 12, 2019 at 4:34 PM Nicola Contu
> wrote:
>
>> P.S.: I am on postgres 11.3
>>
>> Il giorno ven 12 lug 2019 alle ore 16:32 Nicola
On Fri, Jul 12, 2019 at 4:34 PM Nicola Contu wrote:
> P.S.: I am on postgres 11.3
>
> Il giorno ven 12 lug 2019 alle ore 16:32 Nicola Contu <
> nicola.co...@gmail.com> ha scritto:
>
>> Hello,
>> we noticed with a simple matview we have that refreshing it using the
>> concurrently item the space a
P.S.: I am on postgres 11.3
Il giorno ven 12 lug 2019 alle ore 16:32 Nicola Contu <
nicola.co...@gmail.com> ha scritto:
> Hello,
> we noticed with a simple matview we have that refreshing it using the
> concurrently item the space always increases of about 120MB .
> This only happens if I am read
Hello,
we noticed with a simple matview we have that refreshing it using the
concurrently item the space always increases of about 120MB .
This only happens if I am reading from that matview and at the same time I
am am refreshing it.
cmdv3=# SELECT
pg_size_pretty(pg_relation_size('public.matview_
