Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntxGp-0004E1-LH for pgsql-bugs@arkaria.postgresql.org; Wed, 25 May 2022 20:06:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ntxGo-0001YA-6B for pgsql-bugs@arkaria.postgresql.org; Wed, 25 May 2022 20:06:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntxGn-0001Vh-UE for pgsql-bugs@lists.postgresql.org; Wed, 25 May 2022 20:06:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntxGk-0002uR-Qd for pgsql-bugs@lists.postgresql.org; Wed, 25 May 2022 20:06:12 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 24PK692R1999260; Wed, 25 May 2022 16:06:09 -0400 From: Tom Lane To: jampaydavousi@yahoo.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17498: Receive Failed: (error code 1) when importing any csv file from pgAdmin with no explanations In-reply-to: <17498-7b8108cfd105f161@postgresql.org> References: <17498-7b8108cfd105f161@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Wed, 25 May 2022 19:16:17 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1999258.1653509169.1@sss.pgh.pa.us> Date: Wed, 25 May 2022 16:06:09 -0400 Message-ID: <1999259.1653509169@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > Receive Failed: error code 1) when importing any csv file from pgAdmin with > no explanations in the 'Details' section It seems likely that that is a pgAdmin problem, not a problem in core Postgres, in which case this is the wrong place to report it. See https://www.pgadmin.org/support/issues/ instead. If you can reproduce a similarly uninformative failure without using pgAdmin -- say, by using COPY in psql -- then it'd be appropriate for this list to look closer. regards, tom lane