Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfme7-0051lq-8E for pgsql-general@arkaria.postgresql.org; Wed, 05 Feb 2025 21:09:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tfme6-0019MS-D7 for pgsql-general@arkaria.postgresql.org; Wed, 05 Feb 2025 21:09:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfme6-0019MK-2E for pgsql-general@lists.postgresql.org; Wed, 05 Feb 2025 21:09:18 +0000 Received: from mail-yw1-x112e.google.com ([2607:f8b0:4864:20::112e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tfme3-003bke-1A for pgsql-general@lists.postgresql.org; Wed, 05 Feb 2025 21:09:17 +0000 Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-6ef9b8b4f13so2315027b3.2 for ; Wed, 05 Feb 2025 13:09:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738789754; x=1739394554; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0tJZ/FN/oNWkyFU7B36vfiZZ+76Ga7PnvqHU9i7r7II=; b=SOetDLzy+0sNjUv/prM7dkN8Q5eFo6DTVw6/r5cT8AECUMhmhWLzTSzpBeOSRXBJr9 D7zinAOV76X+fgndyfiYZQgnOGXP4jxT5PIKqijWafownwU7m2vm3zm1xC1Uf2HHPlc6 vprrIL0GFfisF+/LYHfOgcznka7gaElEpqYdAiHWe+e91Bh2FEKIOBGAMmWEwIj7ylFO ax9NC3KCt10R0QlIxmI08aseIooJAhi6V9+6+yZ7IMf5alUsJbVfFwh2ri0GHXIK1z/4 bNOHb21uShTtQW4dJ7E/agFbxetf8Lt9TbE2QgpbMm8RsrE5mkR2VbXTlwJPoOEYRb+F XFpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738789754; x=1739394554; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0tJZ/FN/oNWkyFU7B36vfiZZ+76Ga7PnvqHU9i7r7II=; b=JnNKfwZqpBNv3X2d9JKUuYWXzWUL4Iqrc1Y+JKeqtWy4HSkT2r31/GV41Ub7qWHa2c VGUvcYk0NtTIk6G/nZbw5WHnEonbrzWX3F6xUcEUfA61aHRWxxkg88cW1sM6k3xxB7PH ISOrpAcmDXKxhW1YacsUBIOuDQm4qIJuiZ555pKO9ZACXXb1X6RnphnqRXcDY8vaQTrX YCJByzlQUYqQFASBSOFHcEOx8Xe0KQX7By0xMGWf2OF0G35xxySQcV3vJdWY+n8OTShJ mO54KhC47Ln5qDFjBiXKpB/V0uz+ETEYIFsJoJSB5bCbjlAkgNtpqN0pdwmZznHuSov5 Xb8w== X-Gm-Message-State: AOJu0YyovvcgiqXj74iXnSklttQUs4ESU20dmRfIxqJksTpnJeXTtUqC ZCN2sSlGQs533wuWKncS9oO1QKNMB+gY25gxrYLhVK3JLSTQV73ze6ADCa69Pig2oz3WUKL80fn NfKhFlJRQDGM/rQtQeqJAL1Xi2to= X-Gm-Gg: ASbGncsVvFUar4XPvUBtq/l28uhM4+FHojQgFLZz0Rf8US8QV+/oH+4rj4zX+F4I5Wh zB3HM5dGGPfz1vaTNs8ibmhhh9OfOtlQyaNJDkdEbBM/fDJ0I0qNheNBHwQGPz2SPntY72as= X-Google-Smtp-Source: AGHT+IGAFf4Snpeo5gzJfv7NqpSEPsgKxpjlQskRJsah9AKIw8x0/SCbb32+ILJzmDG+8p0iDeywcOtqBlwQG6cX7G0= X-Received: by 2002:a05:690c:4b8b:b0:6f9:54b4:3698 with SMTP id 00721157ae682-6f989eb4585mr46099157b3.13.1738789754425; Wed, 05 Feb 2025 13:09:14 -0800 (PST) MIME-Version: 1.0 References: <0057c073-6dcb-4425-92fc-3a766a78ee96@aklaver.com> In-Reply-To: From: Andy Hartman Date: Wed, 5 Feb 2025 16:09:03 -0500 X-Gm-Features: AWEUYZkpIcedU2ES7MUqdaWwQD6pXJyFq9oXsjLPkJ2a3LkJVzXVaeZiN2wN8H8 Message-ID: Subject: Re: Table copy To: Adrian Klaver Cc: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000a6dbc6062d6b89ce" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a6dbc6062d6b89ce Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I also reduced batch size to 5000 on the last run .. I like using this SImplySql because it's a script I can launch, so that's why I chose that solution... I'm using it to load a History Env. THanks again. On Wed, Feb 5, 2025 at 4:05=E2=80=AFPM Andy Hartman wrote: > nothing in log from mssql side and no anti-virus > > On Wed, Feb 5, 2025 at 2:06=E2=80=AFPM Adrian Klaver > wrote: > >> >> >> 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_0= 3 >> > (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.klaver@aklaver.com >> > --000000000000a6dbc6062d6b89ce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I also reduced batch size to 5000 on the last run=C2=A0 ..= I like using this SImplySql because=C2=A0it's a script I can launch, s= o that's why I chose that solution...=C2=A0 I'm using it to load a = History Env.

THanks again.

On Wed, Feb 5, 2025 = at 4:05=E2=80=AFPM Andy Hartman <hartman60home@gmail.com> wrote:
nothing in log= from mssql side and no=C2=A0=C2=A0anti-virus=C2=A0

On Wed, Feb 5, 202= 5 at 2:06=E2=80=AFPM Adrian Klaver <adrian.klaver@aklaver.com> wrote:


On 2/5/25 9:46 AM, Andy Hartman wrote:
> [6992] ERROR:=C2=A0 unexpected EOF on client connection with an open t= ransaction
> 2025-02-05 12:19:44.919 EST [6992] CONTEXT:=C2=A0 COPY sqlt_data_1_202= 2_03,
> line 24431524, column dataintegrity
> 2025-02-05 12:19:44.919 EST [6992] STATEMENT:=C2=A0 COPY sqlt_data_1_2= 022_03
> (tagid, intvalue, floatvalue, stringvalue, datevalue, dataintegrity, <= br> > t_stamp) FROM STDIN (FORMAT BINARY)
> 2025-02-05 12:19:44.919 EST [6992] FATAL:=C2=A0 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.klave= r@aklaver.com
--000000000000a6dbc6062d6b89ce--