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 1qrDkU-003Cae-I1 for pgsql-odbc@arkaria.postgresql.org; Fri, 13 Oct 2023 08:42:22 +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 1qrDkS-00Fspy-8M for pgsql-odbc@arkaria.postgresql.org; Fri, 13 Oct 2023 08:42:20 +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 1qqwT8-007ZUU-6E for pgsql-odbc@lists.postgresql.org; Thu, 12 Oct 2023 14:15:18 +0000 Received: from mail-pf1-x433.google.com ([2607:f8b0:4864:20::433]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qqwT5-000BnG-BM for pgsql-odbc@postgresql.org; Thu, 12 Oct 2023 14:15:18 +0000 Received: by mail-pf1-x433.google.com with SMTP id d2e1a72fcca58-694ed847889so848083b3a.2 for ; Thu, 12 Oct 2023 07:15:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697120114; x=1697724914; darn=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=qAJFqFJGlN/7dNVaNHgCg0fbcsNdM1Em5sj71DS6+zk=; b=mKWq1cS9rOfT9WgDp4o5vZk+WGoulEQM3h1Q/kmPHztaosj0nyjCs8hYHqivVZpGIW cMcFDhJwUvVQgc9B0zfd3HytDris/jecnVronVywelc1Qt7zSaezZYiIbJaSrZ/MJ81N 8qy/wZjrAUgfkWi5BH5U0WFmxKLfioiPzxCq2LIVSIyDFar+3hoAjIfbuQ59sifh6ODS xZhRfizpJ82Ygh3PG+UzlybOe8QHARKJje0Es0mPm+aAaCAFnKdJrRDRjp8OFE0Jqkhq 2bUNbbcyRVn2f70tVBPXpN5sXus3QkwAGR7ExExgaKQzb5+pOOJGvPXhmBHLLjm32x4A gJIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697120114; x=1697724914; 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=qAJFqFJGlN/7dNVaNHgCg0fbcsNdM1Em5sj71DS6+zk=; b=oV1Xbcoqz85AqQMkbTYE4JSACnf0Kdmbh1yxhQlc5bAeZ1btrNMUg+qunVkphg2Zyq 4fEaueuzmWZFeWFoXgl8u7fHceaNNtA8VmXWKacK/Ivssy7HEE/del571Y+mOygADO3c Ak8nehIzcb+esPcrgb7hTo0vaPPwssyJT/HkrZRgTvJAx8dJQ1KaVtW/h4xfJKUp7SqR bUPaA4fcS3KRZ0P0T4uK9qP/G8Kqvfe/rQjLmSw3FwdUUBgnTN5cB7QxKs3d6Nr9uqc2 g84wGmDla5mQHrNEY8aFqk5UT4VyGwlzMlzMYtm/HQVuPv79nBIxCjYcGkY8OoQpdjV6 V0Eg== X-Gm-Message-State: AOJu0YyqK8Sz59Uureze+m0O/YDkK51e7CBkSuxEshcP5TuDZccJBjDF zI9TKgEsK/KEJcbRd5Q+oxhPfwot9pbeJdMHUcnO+guBQcs= X-Google-Smtp-Source: AGHT+IETgw5pvKKh4fYdnF9nNWhkgmfi6AnDWuRxhxkJXsHX1mTPT8CU5yzoFEWD4L4FT0FfMw7IqHASRqunphVMZyQ= X-Received: by 2002:a05:6a20:7d89:b0:137:23f1:4281 with SMTP id v9-20020a056a207d8900b0013723f14281mr29580429pzj.12.1697120113855; Thu, 12 Oct 2023 07:15:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Victor K." Date: Thu, 12 Oct 2023 17:14:36 +0300 Message-ID: Subject: Re: ODBC error To: Dave Cramer Cc: pgsql-odbc@postgresql.org Content-Type: multipart/alternative; boundary="0000000000008713e806078591ac" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008713e806078591ac Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On servers side logs could not receive data from client connection timed out // (,'')> why? <( )' | | ,,_ _,, =D1=87=D1=82, 12 =D0=BE=D0=BA=D1=82. 2023=E2=80=AF=D0=B3. =D0=B2 16:42, Dav= e Cramer : > > > > > On Thu, 12 Oct 2023 at 09:33, Victor K. wrote: > >> Hello team >> We have error when trying to get data from big table (about 7 GB) >> directly to pivot table in MS Excel 2016 Pro Plus x64 over ODBC driver x= 64 >> Postrge on linux ver 15 >> ODBC psqlodbc_16_00_0000-x64 >> Error >> OLE DB or ODBC error. An error occurred while processing table 'Query'. >> The current operation was cancelled because another operation in the >> transaction failed. >> and >> The commit or rollback request cannot be completed because there is no >> active transaction in this session. >> On small tables everything is okay >> > > I would suggest looking at the server logs. > Dave Cramer > www.postgres.rocks > >> --0000000000008713e806078591ac Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On servers side logs=C2=A0
could not receive data from client co= nnection timed out
=C2=A0//
=C2=A0 (,&= #39;')> why?
<(=C2=A0=C2=A0 )'
=C2=A0=C2=A0 | |
,,_ = _,,


=D1=87=D1=82, 12 =D0=BE=D0=BA=D1=82. 2023=E2= =80=AF=D0=B3. =D0=B2 16:42, Dave Cramer <davecramer@postgres.rocks>:<= br>



=
On Thu= , 12 Oct 2023 at 09:33, Victor K. <ptahin@gmail.com> wrote:
Hello team
We have error=C2=A0w= hen trying to get data from big table (about 7 GB) directly to pivot table = in MS Excel 2016 Pro Plus x64 over ODBC driver x64
Postrge=C2=A0on linux ver 15
ODBC=C2=A0psqlodbc_16_00_0000-x64
= Error
OLE DB or ODBC error. An error o= ccurred while processing table 'Query'. The current operation was c= ancelled because another operation in the transaction failed.
and=C2=A0
= The commit or rollback request cannot be completed because there is no acti= ve transaction in this session.
On= small tables everything=C2=A0is okay

I would suggest looking at the server logs.=C2=A0
Dave Cramerwww.postgres.rocks