| From: | "Arnaud L(dot)" <arnaud(dot)listes(at)codata(dot)eu> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: psql \copy hanging |
| Date: | 2019-08-26 06:57:31 |
| Message-ID: | e9aa5f00-3133-fd2b-9b58-a675db587e47@codata.eu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le 22/08/2019 à 16:23, Arnaud L. a écrit :
> Le 22/08/2019 à 16:21, Adrian Klaver a écrit :
>> The only thing I can think of at the moment is to put the offending line
>> in a separate script and see what happens.
>
> Then I think I'll first try to switch the line orders. I'll execute this
> action last and see if it changes anything. If it doesn't, I'll break
> the script into smaller parts.
It ran fine over the week-end so I'll consider this as temporary glitch.
It's always dissatisfying not to know what has happened, but I'm not
going to try too hard to reproduce this.
Thanks for helping and sorry for the noise !
Cheers
--
Arnaud
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2019-08-26 10:23:44 | Re: For SELECT statement (just a reading one, no 'FOR UPDATE'), is COMMIT or ROLLBACK preferred? |
| Previous Message | Andreas Kretschmer | 2019-08-26 06:49:36 | Re: BDR: moving a node |