Re: \COPY command and indexes in tables

From: Paul Förster <paul(dot)foerster(at)gmail(dot)com>
To: Jayadevan M <maymala(dot)jayadevan(at)gmail(dot)com>
Cc: Matthias Apitz <guru(at)unixarea(dot)de>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: \COPY command and indexes in tables
Date: 2020-11-19 10:17:59
Message-ID: FF8635D9-C088-4E8A-8165-79355EF1F7BC@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Jayadevan,

> On 19. Nov, 2020, at 11:07, Jayadevan M <maymala(dot)jayadevan(at)gmail(dot)com> wrote:
>
> May be you could also make sure that loading actually stopped, by checking the size of the data directory. In another session, you could try
> watch du -h -s <datadirectory>

that might be misleading if you have the pg_wal directory inside PGDATA.

Cheers,
Paul

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Simon Riggs 2020-11-19 11:24:08 Re: Performance degradation with non-null proconfig
Previous Message Jayadevan M 2020-11-19 10:07:19 Re: \COPY command and indexes in tables