Re: DB size growing exponentially when materialized view refreshed concurrently (postgres 9.6)

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Vikas Sharma <shavikas(at)gmail(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: DB size growing exponentially when materialized view refreshed concurrently (postgres 9.6)
Date: 2018-06-25 21:54:15
Message-ID: CAMkU=1ytWhxpngzPGTXa08OXS2K8UoM_ErVdmy7TreVyuZNQkA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 25, 2018 at 1:21 PM, Vikas Sharma <shavikas(at)gmail(dot)com> wrote:

> Hi All,
>
> I am looking for advice in a issue where two materialized views are being
> refreshed concurrently and dbsize has grown to 150gb from 4gb in two days.
>
> We use two materialized views to keep processed data for faster query
> results for a search function. Earlier materialized views were refreshed
> not concurrently and all was good on DB.
>

Where is the space going? Does it show up in psql with \l+ ? Does is show
up in \dm+ ? Does it only show up using OS tools in the data directory?
Which subdirectory of the data directory?

Cheers,

Jeff

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tim Cross 2018-06-25 22:10:29 Re: Using COPY to import large xml file
Previous Message Anthony DeBarros 2018-06-25 20:25:02 PLPython Setup issue with EDB Windows Installer