| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | arnaud(dot)listes(at)codata(dot)eu |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: psql \copy hanging |
| Date: | 2019-08-28 07:43:27 |
| Message-ID: | CAKoxK+6HcC+Qh-nHbgVNkJotH5cjbZjCq1J-z-8cDzY7hTRQnw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Aug 28, 2019 at 9:09 AM Arnaud L. <arnaud(dot)listes(at)codata(dot)eu> wrote:
> OK, so this was enough for last night's schedule to run without problem.
> I still don't get it so I'm not satisfied with this solution, but at
> least it works.
> I'll keep the list informed if something new arises.
I don't want to be pedantic, but I would have tried with a single
change at a time.
And my bet is: the local file would do the trick (i.e., it is a weird
share problem).
If you are going to invest some time, you could also try to write a
small file on the share just before the copy starts, so that you are
guaranteed the share is working. Something like:
echo $(date) >> $SHARE/log.txt
psql 'copy ...'
echo 'done' >> $SHARE/log.txt
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arnaud L. | 2019-08-28 08:13:09 | Re: psql \copy hanging |
| Previous Message | Sonam Sharma | 2019-08-28 07:23:36 | Re: vaccum in background |