From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | arnaud(dot)listes(at)codata(dot)eu, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: psql \copy hanging |
Date: | 2019-10-10 14:37:12 |
Message-ID: | 892b0583-1ac1-cd68-c37b-34fad6b05284@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/10/19 12:00 AM, Arnaud L. wrote:
> Le 08/10/2019 à 16:59, Arnaud L. a écrit :
>> Yes, I already did that, and unfortunately there's no activy.
>> There is absolutely no activity in procmon using psql.exe as a filter.
>> process-xp is not giving more information, processor usage is 0%.
>
> My apologies, I obviously did something wrong last time I checked this
> process with process-xp and procmon.
> Now I see that there IS activity on the problematic process !
> 100% CPU and some (but not much) disk activity.
>
> I think I'll try to let it run for some time to get the auto_explain do
> its work. If I kill the backend now, I won't see anything I believe.
You can look at:
pg_locks
https://www.postgresql.org/docs/11/view-pg-locks.html
and
pg_stat_activity
https://www.postgresql.org/docs/11/monitoring-stats.html#PG-STAT-ACTIVITY-VIEW
in real time to see if there is any useful information.
>
> I dont now it it'll ever complete this query though, it usually takes
> ~100 seconds, and here it has already been running for 9 hours.
>
> Regards
> --
> Arnaud
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2019-10-10 15:02:22 | Re: SOLVED Re: Recovering disk space |
Previous Message | Stephen Frost | 2019-10-10 14:35:04 | Re: Is my lecturer wrong about PostgreSQL? I think he is! |