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 1rBzbL-00DGYy-1r for pgsql-general@arkaria.postgresql.org; Sat, 09 Dec 2023 15:50:47 +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 1rBzbJ-001QrC-NE for pgsql-general@arkaria.postgresql.org; Sat, 09 Dec 2023 15:50:45 +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 1rBzbH-001Qqu-Ti for pgsql-general@lists.postgresql.org; Sat, 09 Dec 2023 15:50:45 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rBzbC-00B1ma-3y for pgsql-general@lists.postgresql.org; Sat, 09 Dec 2023 15:50:43 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 429A73200A76; Sat, 9 Dec 2023 10:50:34 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sat, 09 Dec 2023 10:50:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1702137033; x=1702223433; bh=mDfyuaR4estoiTgXTXCmcgkE0leMMhRR1ZQ azAyNvYQ=; b=u+imFkSjVKjjPc3IoJB0WBa0N9mVbfRTYF4TsipUQN1/6U9K80Y UUtXUmt3shtPZ/jvvZVlOR37Qwm9ASIZmEGDZoUu6KFbA1kbx+JawdEXXKlSJkE6 ECqkyN5fElYPfrDA/m1UBGrwz8UXLnLg8zgsvEVNkRXhrr5ITS8zPYlyG7lh8nhz 1HFOVJKO/2p/hOmU0P+nviJeFkoE51mZ3Cy5ySQOrT4SCqGCpcBz75FkMqzMEACw Q97yTAJNeabwSFGJiGCL7WfGkHu7qXCnrj6zEQoiKmucsGhvfUN4QvJpg81PGcYl 7E/CQC0oLNqr3JnqRpraPW8+/UKgZFvjDxg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1702137033; x=1702223433; bh=mDfyuaR4estoiTgXTXCmcgkE0leMMhRR1ZQ azAyNvYQ=; b=bzFdNaXx35kmbL1kk1pH2sobm8CqmAdFqPd1eZYCqyx6brD4jFK y/N7xHWUNIwl3CiSX1EAOCR0zsSehoIngDsZ+tJYMKlALHFkF0TMydgYOvJoa/fy AWlfpRy+bXx+ZGQ7irLj5IuM7xIT0xRk3aGE6uxDMLcYafKB1Hu9eybkrayiqeqA 7g7noOu7KwvhOGDL356GRlchQ2xUOmFxzUUNkdXJZtBesa694hCm1Q0Mp87ZXYyK GdvfiXNmgWcmgg3JKT6FCLeGtwhpLktq6JqgyJTOiKkO6ikm71jjsxEG9iZc2z08 52Lfqcg1Yd2MMtcqkPsjl7X+kHD20sa2PKw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudekkedgkedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepfeegfeeiuedtgffgteeggfehkeejheetieeliefg teeikeejvdeiveeigfehvedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 9 Dec 2023 10:50:33 -0500 (EST) Message-ID: <79c4fe6d-7efe-40dc-bb4d-fb3399bc5c92@aklaver.com> Date: Sat, 9 Dec 2023 07:50:32 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: how can I fix my accent issues? To: Igniris Valdivia Baez , Laurenz Albe Cc: pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12/9/23 07:41, Igniris Valdivia Baez wrote: > hello, thank you for answering, it's not a typo, in the attachments > you can see that this is actually my collation, algo a pic of the > problem for more clarification, > thank you all You picture shows the database collation as Spanish_Cuba.1252 not the Spanish_Cuba.1952 you originally indicated. 1) Which is the above for the production database or the dev one? 2) What are the exact settings for the other database? > best regards > > El sáb, 9 dic 2023 a las 1:01, Laurenz Albe > () escribió: >> >> On Fri, 2023-12-08 at 23:58 -0500, Igniris Valdivia Baez wrote: >>> hello, I have an ETL process collecting data from a postgresql >>> database and xls files and inserting in a postgresql database that >>> process occurs great in a local DB in postgres 14 with UTF8 >>> codification and Spanish_Cuba.1952 collation but when I execute that >>> process in dev which is in postgres 15 and UTF8 with collation >>> en_US.utf8 the words with accents and ñ looks like an interrogation >>> symbol, what can I do to fix this? >> >> If the data you are sending are encoded in WINDOWS-1252 (I assume that >> "1952" is just a typo), you should set the client encoding to WIN1252, >> so that PostgreSQL knows how to convert the data correctly. >> >> You can do that in several ways; the simplest might be to set the >> environment variable PGCLIENTENCODING to WIN1252. >> >> Yours, >> Laurenz Albe -- Adrian Klaver adrian.klaver@aklaver.com