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 1tQ6ys-000AHm-7u for pgsql-general@arkaria.postgresql.org; Tue, 24 Dec 2024 15:37:58 +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 1tQ6yp-006Dsc-L2 for pgsql-general@arkaria.postgresql.org; Tue, 24 Dec 2024 15:37:55 +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 1tQ6yp-006DsS-AP for pgsql-general@lists.postgresql.org; Tue, 24 Dec 2024 15:37:55 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tQ6yl-001PJp-9M for pgsql-general@lists.postgresql.org; Tue, 24 Dec 2024 15:37:53 +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 4BOFbniO1613090; Tue, 24 Dec 2024 10:37:50 -0500 From: Tom Lane To: Olleg Samoylov cc: pgsql-general@lists.postgresql.org Subject: Re: "trailing junk after numeric literal at or near ""512""" In-reply-to: References: Comments: In-reply-to Olleg Samoylov message dated "Tue, 24 Dec 2024 08:46:09 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1613088.1735054669.1@sss.pgh.pa.us> Date: Tue, 24 Dec 2024 10:37:49 -0500 Message-ID: <1613089.1735054669@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Olleg Samoylov writes: > I have PostgreSQL 16.6. The log files are attached as partitions by > file_fdw to the SQL table. Common practice. But after the error message > "trailing junk after numeric literal at or near ""512""" (vim -b view) > was wrote, the reading all log was stopped with error from file_fdw: > ERROR: invalid byte sequence for encoding "UTF8": 0xd0 0x22 > The reason is the error message in the log file (which must be utf-8) > consist of: > \x 22 35 31 32 d0 22 > " 5 1 2 " > and d0 is not a utf-8 character so it block reading whole log file by > file_fdw. You certain that server is 16.6? Because we fixed that in 16.5: https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=4fd4d7653 regards, tom lane