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 1t8ZBE-004sLi-Qq for pgadmin-support@arkaria.postgresql.org; Wed, 06 Nov 2024 06:06:12 +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 1t8ZBC-003p36-8F for pgadmin-support@arkaria.postgresql.org; Wed, 06 Nov 2024 06:06:10 +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 1t8ZBB-003p2x-W8 for pgadmin-support@lists.postgresql.org; Wed, 06 Nov 2024 06:06:10 +0000 Received: from mail-lj1-x230.google.com ([2a00:1450:4864:20::230]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t8ZB8-000QLv-Ak for pgadmin-support@postgresql.org; Wed, 06 Nov 2024 06:06:09 +0000 Received: by mail-lj1-x230.google.com with SMTP id 38308e7fff4ca-2fc968b3545so61611681fa.2 for ; Tue, 05 Nov 2024 22:06:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1730873164; x=1731477964; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+sFQvoqldM69/cvDmqQjtWasFhPGuUX8+iaAVVmC01U=; b=cRuZ/BFGUYsIU2pF8xvjw/1DyY8TXuoIyESnswVzfXY3QHZl1iu3UhImnEfTmA1MfH g2baaffwSbCYBVu+b3VPbzyBqj6oX4uz7Vs6MiW6uwL0rJB/T4uKe3IQCg3iAdoF+pJI tZxnJWWzeGUdwWTXL7wqwY5zkAnIoEc2hOTpD/RH2fq5XWWDnjGP6TTaoyFLwmUTKqAK N9CS6vRCtZZTcN9cU4a3iBPuf7xNoSpLdYElmAthZX272aiHbr8KY0CEfip8FKQFPev6 5zFIZPf7IXI4AeSF3O7rOFLRc0L5c062hnHsk+3lFKvlvzKX1k3sOCxtumGsLHx/sDFr mT0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730873164; x=1731477964; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+sFQvoqldM69/cvDmqQjtWasFhPGuUX8+iaAVVmC01U=; b=XanF/Rpg9ZPwhNYWjE3iUzOYBQHLGCduCMd4rmymzQPaY7STuJRzSz8s/674gMEqvl RPQzkW1DXaZsQylyhZF4sb1npUx4ulaaSz3SywFgsBN/6v3e1RxI8sl5fW53J6wlgNp3 RR1EaAMjXraZLmYntBnGeyW5ZZIwcxfyaFclCB0pdmHsJWViMhaLw2PjK5Ocofo1SQZK sFAHIUOCWEFYJzQHJJepa/Mt7zhuvgD9N7Ex1FMEy+DkeYBcPEqRlCKS+C/kPyaLgtwX m8F4RIzsQziquxJ6d3Te+b++YFd40MQm/VsRbdjKvaDHVKq0j05qTzDQSeTaSmLq1cXQ +rmA== X-Gm-Message-State: AOJu0Yz/9VyqTvAZoKZiZhGzYltvEgYk03WD2hrYSXGBNKEw42NL9gOl iq+c8BW6++kR+RKl0cC8Sgl8KMbP4vzA8y6y/aP9ny39W0LMdqa2wysjaL2Vm3PJh6dgWsFVUA/ Zgs3Cy/VWOQEg6a/eZallWSOg908EuyCxRUh7mUqNDaD3CuCDUGoq X-Google-Smtp-Source: AGHT+IFADyNSyeb5u8OV4Q7ISCpusmGMpOcH2SAWHqMd4Cxn9ZG7Fy5uFRvnNYdTMcW9BN1Z+3GWBVHIF8E/eva2p5U= X-Received: by 2002:a2e:a541:0:b0:2fb:6328:b633 with SMTP id 38308e7fff4ca-2fdec47a5abmr99406081fa.4.1730873164261; Tue, 05 Nov 2024 22:06:04 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Akshay Joshi Date: Wed, 6 Nov 2024 11:35:53 +0530 Message-ID: Subject: Re: Feature request - Pg 17 builtin locale provider To: Darren Duncan Cc: pgAdmin Support Content-Type: multipart/alternative; boundary="0000000000001b8db8062638504f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001b8db8062638504f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Darren Please create a feature request at https://github.com/pgadmin-org/pgadmin4/issues/new/choose On Wed, Nov 6, 2024 at 12:05=E2=80=AFAM Darren Duncan wrote: > I'm using the latest pgAdmin and notice that its "create database" GUI > feature > lacks the new "builtin" option of Postgres 17 for locale provider and > related > options like "C.UTF-8" so I could only create a database with the > "builtin" > provider using hand written SQL. > > https://www.postgresql.org/docs/current/sql-createdatabase.html > > Also, a word of warning, apparently I can only create a database with tha= t > locale if "template0" is used as the baseline, and not "template1" as it > comes > from the factory. > > Can support for this feature etc be added to the next pgAdmin version? > > Thank you. > > -- Darren Duncan > > > > > --0000000000001b8db8062638504f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Darren

Please create a feature reque= st at=C2=A0https://github.com/pgadmin-org/pgadmin4/issues/new/choose

On= Wed, Nov 6, 2024 at 12:05=E2=80=AFAM Darren Duncan <darren@darrenduncan.net> wrote:
I'm using the latest pgA= dmin and notice that its "create database" GUI feature
lacks the new "builtin" option of Postgres 17 for locale provider= and related
options like "C.UTF-8" so I could only create a database with the= "builtin"
provider using hand written SQL.

https://www.postgresql.org/docs/curre= nt/sql-createdatabase.html

Also, a word of warning, apparently I can only create a database with that =
locale if "template0" is used as the baseline, and not "temp= late1" as it comes
from the factory.

Can support for this feature etc be added to the next pgAdmin version?

Thank you.

-- Darren Duncan




--0000000000001b8db8062638504f--