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 1t51sy-003esu-CL for pgsql-general@arkaria.postgresql.org; Sun, 27 Oct 2024 11:56:44 +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 1t51sv-00GBFM-7S for pgsql-general@arkaria.postgresql.org; Sun, 27 Oct 2024 11:56:41 +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 1t51su-00GBFD-Si for pgsql-general@lists.postgresql.org; Sun, 27 Oct 2024 11:56:41 +0000 Received: from mail-oo1-xc30.google.com ([2607:f8b0:4864:20::c30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t51ss-0036i4-MF for pgsql-general@postgresql.org; Sun, 27 Oct 2024 11:56:40 +0000 Received: by mail-oo1-xc30.google.com with SMTP id 006d021491bc7-5eb67d926c4so1550097eaf.0 for ; Sun, 27 Oct 2024 04:56:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730030198; x=1730634998; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=HOxqGujLsQ6wP+bYAvN0Z4Gz6X85MQwLJshshaD+Az8=; b=lwuaQ8Q48LKNFL9jZSjMsvXe5zCmqA+BQVeWqZZGBHk67evOtxzfJkEV8REicWDbo1 +uMIfmsvG6dxlVNEvk6xMaGYeze8fMSra5CuC1GwjmqltkkXf0miOW3/8zOPM2eO2jGU w3zCHsFlBrClqjuvtrIAwdvHJ0DIBxm745jINTTsy6tzG+CVSHjXJ9fbqN/DvFo5Kt2M rhIRwwP81elvlPo9xWrOUClnWIKfgNIlbTzOO7CPycY93y6A5dhRgS6WaUJaIxEdfO0o 1HhfD9iNta1dFFSn0crPMXxi8OAdmQ1WEkIH0rhCFwDVMLal8f0TtI4Dqckz/S3FpU2a 49QQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730030198; x=1730634998; h=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=HOxqGujLsQ6wP+bYAvN0Z4Gz6X85MQwLJshshaD+Az8=; b=LSEi/ktEi+JtGhHpaYV+CP/CtGM19NVAOYg1xwyRImAe9bmQanZK3QDPhSSWjjhG9s 71wEVMyfy3lfytNzJPU6WcwtY4J8EQRUqrTbqHxY98dCchkTxITuajpcxxFWCqQWxE/f 07IBDsFhUcTO0qD8Vlqq0blAlYG1Mlo8D1n+XV4auRp5/Zv8g4nzKlpRq2I5srLVBHPV um1QWCCHP0S2XnR237fWNvXGEDgwE/ZfRMqRrm3GUkyomrLUw9H/t5tesHeO5DXGHmej QhY0vGWVRNosjfsa6uXjdlj3babq/tBALsWDERjTILpxceUf3zvQ1n3neQnwFdgiPhj2 VHJA== X-Gm-Message-State: AOJu0YwRKBpQB/P/KoJlWEk7UEJFKtF0s4U/bX5VLNPc2s2sicXWc5UT GVv3XCqXX+uFhn7S3/omEZdQdPsPfWGXf/RiXZ2eqrt61azn+oQn/WESaiPdtF7nHdSCEC9iVgw aRlRUfMoS9haU6X0JK+Lp10Y1uFI1Md7z X-Google-Smtp-Source: AGHT+IFzW5H8g5Y/J2c1jUiJeTLVAc/0xC7xSZ185nA0XXAibfWtbEvq1vHrfgThnygUbNuN5yistgGge1c2HPB6WFI= X-Received: by 2002:a05:6820:1ad6:b0:5eb:6b3e:ce7f with SMTP id 006d021491bc7-5ec22bb0807mr2398216eaf.0.1730030197717; Sun, 27 Oct 2024 04:56:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Sun, 27 Oct 2024 07:56:26 -0400 Message-ID: Subject: Re: Setting "ucs_basic" as the default database collation To: pgsql-general Content-Type: multipart/alternative; boundary="00000000000062c4a80625740b8b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000062c4a80625740b8b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Oct 27, 2024 at 5:32=E2=80=AFAM Christophe Pettus wrote: > Is there a way to specify "ucs_basic" (or the other "standard collations" > [1]) collation as the default database collation at database creation tim= e, > rather than on a per-column or per-operation basis? > > [1] > https://www.postgresql.org/docs/current/collation.html#COLLATION-MANAGING= -STANDARD > > https://www.postgresql.org/docs/16/sql-createdatabase.html The CREATE DATABASE statement has an ENCODING option. Does that work with 'ucs_basic'? --=20 Death to , and butter sauce. Don't boil me, I'm still alive. crustacean! --00000000000062c4a80625740b8b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Oct 27, 2024 at 5:32=E2=80=AFAM C= hristophe Pettus <xof@thebuild.com> wrote:
The CREATE DATABASE statem= ent has an=C2=A0ENCODING=C2=A0option.=C2=A0 Does that work wi= th 'ucs_basic'?

--
Death to <Redacted>, and butter sauce.
Don't boil me, I= 'm still alive.
<Redacted> crustacean!

--00000000000062c4a80625740b8b--