| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | 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 07:57:33 |
| Message-ID: | 044d427bf8a91959da6cb20394c166be734afe02.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2020-11-19 at 08:38 +0100, Matthias Apitz wrote:
> We load large tables in some customer installation (some millions of rows)
> from file with:
>
> TRUNCATE TABLE tableName ;
> \COPY tableName FROM 'fileName' WITH ( DELIMITER '|' )
>
> and got to know that the loading nearly stops (without any real CPU
> consumption) in the middle. The wild guess is that we forgot to DROP the indexes on
> the tables.
If it does not consume CPU, it must be stalled somehow.
Are there any wait events in "pg_stat_activity".
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atul Kumar | 2020-11-19 08:05:22 | maintenance_work_mem |
| Previous Message | Matthias Apitz | 2020-11-19 07:38:45 | \COPY command and indexes in tables |