| From: | "Arnaud L(dot)" <arnaud(dot)listes(at)codata(dot)eu> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: psql \copy hanging |
| Date: | 2019-10-08 14:59:55 |
| Message-ID: | b21e1847-d05b-d91f-284a-41f5a4e7b427@codata.eu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le 08/10/2019 à 16:55, Daniel Verite a écrit :
> Arnaud L. wrote:
>
>> Anyway, it hung using this syntax during last night's run.
>> I'll give it another try tonight just to be sure.
>
> When psql.exe is hanging, maybe you could use a tool like
> Process Monitor [1] or Process Explorer [2] to get insights about
> what it's stuck on or what it's doing exactly.
>
> [1] https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
> [2] https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
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%.
Regards
--
Arnaud
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-10-08 15:02:31 | Re: Table locking during backup |
| Previous Message | Daniel Verite | 2019-10-08 14:55:18 | Re: psql \copy hanging |