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 1rL3xj-005uQm-I7 for pgsql-general@arkaria.postgresql.org; Wed, 03 Jan 2024 16:19:24 +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 1rL3xi-006LDD-7u for pgsql-general@arkaria.postgresql.org; Wed, 03 Jan 2024 16:19:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rL3xg-006LD5-Br for pgsql-general@lists.postgresql.org; Wed, 03 Jan 2024 16:19:21 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rL3xc-00DYdG-LG for pgsql-general@lists.postgresql.org; Wed, 03 Jan 2024 16:19:19 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id CA6DE5C00E2; Wed, 3 Jan 2024 11:19:14 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 03 Jan 2024 11:19:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= 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:subject:subject:to:to; s=fm1; t=1704298754; x=1704385154; bh=EaWGOg+YJya9pXmg1FsnbWkEEsLMwH+kAc4AszsBP9o=; b= MdOiJgJitIzzeVBZDzh4Y2JXfRdqYIdsdRiq1vTodWxSFLzMvC2njl3j5SScjecG s+0LxKVMJIlOfK0fTHFXTqae6g9bk6xI1EGQQry4b9Wwo6cqzm7ykENQkRhESmA2 q8wsEzt+FsPPp1+qq9ODWeRiPc7QG0rFhGsumekPDK/cmNA8GOuWNxUh8PNsE+Do UbO2XOhOgkvujywZNugsXRe8I0+n5qRTT93Fakb/0TGdJ9UJt2hD/FACS2498KtM 0+spv8jtYlZDJOmopJ/IjdpjPEe0mU1R08RC/Vsw3id9pxQJq9I6lIQaW8oLUNF4 25g2oOANkBcPI49brUhLVw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1704298754; x= 1704385154; bh=EaWGOg+YJya9pXmg1FsnbWkEEsLMwH+kAc4AszsBP9o=; b=I JZKe8/K+FZ1icuccDoJViYJsg6RGDztgU3a5pOr8Gvrqz9+C7lwqMwpXstxTXXsK BDdlFGX3cxmygkUG/MF/H1vLyiw4lo8aL8tO/GLiw058hEUgItkeUz2L4Cj5nU9l sE9DsXTfHSf0rHOvFgiZzgdcU7yNIeAW32r7QE6TrNp8Dsb/7+xWtebCbWqqkFdD 76fY9I6HzVzWsFae1Qhny7GEgvlBa+PyZBhbSmXGp0WIYGvGUlW3umgANOnYwHkE oJfsGczwkpy7GYZcV4T5pX0MpeA0iIRgb6ST4Gs4XZnwo2UdilZ3SKIVgQR01dEb SZJcGRAFAlEtJhCwut3sg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdeghedgkeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtvdejnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhk lhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepkeeugeehje fgkeefffdtudevheeilefgheevgfeljefhtdeikedvieefheffgfeinecuffhomhgrihhn pehpghgrughmihhnrdhorhhgpdhpohhsthhgrhgvshhqlhdrohhrghenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghv vghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 3 Jan 2024 11:19:13 -0500 (EST) Message-ID: <158125d0-fd85-4309-a080-ece96ec8a5d9@aklaver.com> Date: Wed, 3 Jan 2024 08:19:12 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: encoding option when database backup To: Taek Oh , rob stone , pgsql-general@lists.postgresql.org References: <6bb945dd0987c5b7ac0002b5b9c917706d63770e.camel@tpg.com.au> 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 1/3/24 05:14, Taek Oh wrote: > Thank you Rob for your response. > > Unfortunately, the Encoding drop-down listbox does not exist for the > pgadmin V8. > Therefore, I would like to seek a way to activate the listbox or select > the encoding method during the Backup procedure. 1) Per https://www.pgadmin.org/docs/pgadmin4/8.1/backup_server_dialog.html "Use the Encoding drop-down listbox to select the character encoding method that should be used for the archive. Note: This option is visible only for database server greater than or equal to 11." So are you trying to backup a Postgres version older then 11? 2) pgAdmin is a separate project from the Postgres server. If you are trying to back from a Postgres 11+ server and don't see the encoding dropdown then you should probably bring that up on: https://www.postgresql.org/list/pgadmin-support/ > > Regards, > > Taek > > On Wed, Jan 3, 2024 at 4:19 PM rob stone > wrote: > > > > On Wed, 2024-01-03 at 15:59 +0900, Taek Oh wrote: > > Hi there, > > > > I would like to make an inquiry regarding the encoding option for the > > database backup. > > When I was using the previous version of PGADMIN 4, I had a > > dropbar for the encoding format for the backup option. > > But I recently started using the latest version of PGADMIN 4(V8.1), > > and I realized that the dropbar for encoding format has disappeared > > as we can observe from the attached image. > > Are there any solutions where I can activate the encoding dropbar? > > > > Thank you in advance, > > > > Taek > > > > > > > See https://www.pgadmin.org/docs/pgadmin4/latest/backup_dialog.html > > where it mentions:- > > Use the Encoding drop-down listbox to select the character encoding > method that should be used for the archive. > > -- Adrian Klaver adrian.klaver@aklaver.com