From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | arnaud(dot)listes(at)codata(dot)eu |
Cc: | 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 07:28:19 |
Message-ID: | CAFj8pRCbOidyOMJ_0TPYdm0xKAJ2sHpC3VQdB_Mn05W0vgCF7g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
út 8. 10. 2019 v 9:06 odesílatel Arnaud L. <arnaud(dot)listes(at)codata(dot)eu> napsal:
> Le 07/10/2019 à 16:36, Adrian Klaver a écrit :
> > So you are saying that you have not run the problematic line by itself?
>
> It hung during last night's run.
>
> I had modified my batch script to run the \copy commands separately,
> i.e. it now reads as :
> psql -h myserver -a mydb < originalscriptwithoutproblematicline.sql
> psql -h myserver -a mydb < problematicline.sql
>
> It hung at the problematic line, so during the second psql command.
>
> I'm really at loss... I *believe* that the problem lies either in psql
> or in PostgreSQL, but I really don't know what to try now.
>
you can write simple C application with COPY API
https://www.postgresql.org/docs/12/libpq-copy.html
Then you can eliminate or ensure locality of problem.
more, you can use server side copy. Superuser can read data from server
file system.
Regards
Pavel
>
> Regards
> --
> Arnaud
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Arnaud L. | 2019-10-08 09:47:56 | Re: psql \copy hanging |
Previous Message | Arnaud L. | 2019-10-08 07:06:41 | Re: psql \copy hanging |