Feedback-ID: i76984098:Fastmail
Message-ID: <fd275e8a-80fa-4915-8aa3-9b48728d562a@aklaver.com>
Date: Tue, 4 Feb 2025 12:02:19 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Table copy
To: Andy Hartman <hartman60home@gmail.com>,
 "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: <CAEZv3cqo3rze3SQUqLCNq7gbnQiDusCD4R+55UW3VtuZZeJQBg@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAEZv3cqo3rze3SQUqLCNq7gbnQiDusCD4R+55UW3VtuZZeJQBg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/fd275e8a-80fa-4915-8aa3-9b48728d562a%40aklaver.com>
Precedence: bulk


On 2/4/25 11:51 AM, Andy Hartman wrote:
> I'm copying a large table from mssql to PG using SImplysql and in the 
> Log I see this message
> 
> 2025-02-04 14:42:17.975 EST [4796] ERROR:  unexpected EOF on client 
> connection with an open transaction

The above pretty much spells it out.

Something messed with the connection from the client.

You need to look at Postgres and system logs to see if you can track 
down what?

FYI, more information would be helpful:

1) MS SQL version.

2) Postgres version.

3) SimplySQL version.

4) The complete copy command.

5) The amount of data being transferred.

6) The OS'es and their versions on both ends.


> 2025-02-04 14:42:17.975 EST [4796] CONTEXT:  COPY sqlt_data_1_2022_03, 
> line 208274199, column tagid
> 2025-02-04 14:42:17.975 EST [4796] STATEMENT:  COPY sqlt_data_1_2022_03 
> (tagid, intvalue, floatvalue, stringvalue, datevalue, dataintegrity, 
> t_stamp) FROM STDIN (FORMAT BINARY)
> 2025-02-04 14:42:18.158 EST [4796] FATAL:  terminating connection 
> because protocol synchronization was lost
> 2025-02-04 14:42:18.265 EST [4796] LOG:  could not send data to client: 
> An established connection was aborted by the software in your host machine.
> it then dies with a data stream error.I have copied other tables on this 
> size with no problems.
> 
>   THanks.
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com