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.96) (envelope-from ) id 1weDea-004eJe-0K for pgsql-bugs@arkaria.postgresql.org; Mon, 29 Jun 2026 15:12:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1weDeY-003pHn-2h for pgsql-bugs@arkaria.postgresql.org; Mon, 29 Jun 2026 15:12:06 +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.96) (envelope-from ) id 1weDPC-003n4l-08 for pgsql-bugs@lists.postgresql.org; Mon, 29 Jun 2026 14:56:14 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1weDP8-00000000noW-3Kby for pgsql-bugs@lists.postgresql.org; Mon, 29 Jun 2026 14:56:13 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=qWUb1uMop60DwABQDcl1ueRmda4N+DGfD7/GPQe5huw=; b=2JzH54zuQbomX6HeQ8jpSLJNrO aD+Lq4kEh+bZLHiLfCKnEY8meeaTpnAzcTzoyP9sCqZGwNPTBppcWYaPQJqTJQ+MNqybuLB2nYrPY o71cWVwTjLPsKzb2qo+Dupw5gmzeo/GPeOggN30fZAlXAhKw0M3uJCXhj6gGsHlzzOfNwAUNWBgv3 XtSbVAiEwoZEtCFi93XcMdwJPw/vfkI5ArTa7Lizw6bjUVXzG9fl16TezGUFLsN30MX6BVVUGPhvH XuJLkMQGyB8T1RAZ2YqB4R1OYrjB6h85P3H0UZ9GAR5ow2EA5p0PI7zxJL22zJCFb+UatOwBK4kfA OdzahHQA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1weDP7-008Ims-0y for pgsql-bugs@lists.postgresql.org; Mon, 29 Jun 2026 14:56:09 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1weDP1-005vU8-05 for pgsql-bugs@lists.postgresql.org; Mon, 29 Jun 2026 14:56:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19539: psql 17.6 on Windows 11 prints random garbage characters in Russian localized output of \d To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: adyakovam@gmail.com Reply-To: adyakovam@gmail.com, pgsql-bugs@lists.postgresql.org Date: Mon, 29 Jun 2026 14:55:10 +0000 Message-ID: <19539-938dea64f871c379@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19539 Logged by: Maria Adyakova Email address: adyakovam@gmail.com PostgreSQL version: 17.6 Operating system: Windows 11 Description: =20 Environment PostgreSQL: 17.6 psql: 17.6 Windows 11 Official EnterpriseDB installer UTF-8 console (code page 65001) server_encoding =3D UTF8 client_encoding =3D UTF8 Description When running \d in Russian localization, the output sometimes contains random garbage Unicode characters immediately after the localized header "=D0=9F=D0=BE =D1=83=D0=BC=D0=BE=D0=BB=D1=87=D0=B0=D0=BD=D0=B8=D1=8E= ". Example: =D0=A2=D0=B0=D0=B1=D0=BB=D0=B8=D1=86=D0=B0 "public.articles" =D0=A1=D1=82=D0=BE=D0=BB=D0=B1=D0=B5=D1=86 | =D0=A2=D0=B8=D0=BF | =D0=9F= =D1=80=D0=B0=D0=B2=D0=B8=D0=BB=D0=BE =D1=81=D0=BE=D1=80=D1=82=D0=B8=D1=80= =D0=BE=D0=B2=D0=BA=D0=B8 | =D0=94=D0=BE=D0=BF=D1=83=D1=81=D1=82=D0=B8=D0=BC= =D0=BE=D1=81=D1=82=D1=8C NULL | =D0=9F=D0=BE =D1=83=D0=BC=D0=BE=D0=BB=D1=87= =D0=B0=D0=BD=D0=B8=D1=8E =E2=AB=90=E9=84=A2=CA=A7 The garbage characters change every execution. Switching the locale to English: set LANG=3DC completely eliminates the problem. The issue reproduces even when starting psql with: psql -X so it does not appear to be related to user configuration. Expected behavior: No extra characters after the localized header. Actual behavior: Random Unicode garbage appears after "=D0=9F=D0=BE =D1=83=D0=BC=D0=BE=D0=BB= =D1=87=D0=B0=D0=BD=D0=B8=D1=8E" on every invocation.