| From: | "Arnaud L(dot)" <arnaud(dot)listes(at)codata(dot)eu> |
|---|---|
| To: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: psql \copy hanging |
| Date: | 2019-08-27 11:17:17 |
| Message-ID: | 574a09e0-cf01-4664-c61c-c2d0ae9300f9@codata.eu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le 27/08/2019 à 13:13, Luca Ferrari a écrit :
> My personal experience with shares and network that are not so much
> stable is that they can block, and that is why I'm suggesting to try
> on the local filesystem to see if that is a share-related problem or a
> resource problem. Also scheduling the script at a different time could
> help, because it could be at that time the machine (and it could mean
> the sharing machine) is busy at the point it does not respond.
I'm quite confident that changing the schedule would help (since the
script runs fine during work hours), but the time-table is already quite
busy.
I move the offending line at the end of the script, so it will run some
minutes later, maybe this will be enough.
I'll also try to write it directly on a local folder to rule this out.
Cheers
--
Arnaud
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2019-08-27 11:28:13 | Re: Pointers towards identifying bulk import bottleneck (walwriter tuning?) |
| Previous Message | Luca Ferrari | 2019-08-27 11:13:27 | Re: psql \copy hanging |