| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Andy Hartman <hartman60home(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Table copy |
| Date: | 2025-02-05 19:06:16 |
| Message-ID: | ae581d81-3d0a-471b-9dc5-e23d98ee1fe6@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/5/25 9:46 AM, Andy Hartman wrote:
> [6992] ERROR: unexpected EOF on client connection with an open transaction
> 2025-02-05 12:19:44.919 EST [6992] CONTEXT: COPY sqlt_data_1_2022_03,
> line 24431524, column dataintegrity
> 2025-02-05 12:19:44.919 EST [6992] STATEMENT: COPY sqlt_data_1_2022_03
> (tagid, intvalue, floatvalue, stringvalue, datevalue, dataintegrity,
> t_stamp) FROM STDIN (FORMAT BINARY)
> 2025-02-05 12:19:44.919 EST [6992] FATAL: terminating connection
> because protocol synchronization was lost
You need to look at the other end of the connection also, in other words
what is happening on the MS SQL Server 2016/Windows Server 2019 side?
Also is there anti-virus software running on either end?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thiemo Kellner | 2025-02-05 20:15:41 | Re: Lookup tables |
| Previous Message | Michał Kłeczek | 2025-02-05 18:13:49 | Re: Lookup tables |