Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntkg9-0006eQ-1n for pgsql-admin@arkaria.postgresql.org; Wed, 25 May 2022 06:39:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ntkg7-0000T2-TQ for pgsql-admin@arkaria.postgresql.org; Wed, 25 May 2022 06:39:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntkg7-0000St-EV for pgsql-admin@lists.postgresql.org; Wed, 25 May 2022 06:39:31 +0000 Received: from mail-ed1-x52c.google.com ([2a00:1450:4864:20::52c]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ntkg3-0000Yk-54 for pgsql-admin@lists.postgresql.org; Wed, 25 May 2022 06:39:31 +0000 Received: by mail-ed1-x52c.google.com with SMTP id s3so25737647edr.9 for ; Tue, 24 May 2022 23:39:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=peoKPqI+mp1n2dciD7NGqSL2crPnK0S0ZEK60TE5fys=; b=fy+WfRrUMcbGAL1q3pHfroWG/tBpxfXzMiAMj4208vlQRfomlLGPM6FceqihcTo/ak Hdu24KUOr4I+Gc97rhTcYu/42NxcbJ7Ggosa26mTBDkIwn7MX8ogYmuRgsPlzRciRMe4 rNLRedNGp+/d9BU8x1nKJnF0tOwjE3ZQLx+qmcfyO/0e+cx0jZVlnJI1kUgC8p6JdtQS YQ9Swpl2IEH/SOAMBEcxTfpg3VbKrDhlllpYErUmWLPGq4GnAqgOgHuhPWu7NVbj12Lf 2zitRHnM6IM4RFdkA8N6S/uh9880KMHaIudLnq4GsIdewwBfjuZg07AjEH8K0GeTEJGG kQXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=peoKPqI+mp1n2dciD7NGqSL2crPnK0S0ZEK60TE5fys=; b=tm4RKV0Xe6k7kSRgb7wuisP/2ZWhR1DnF5PXTPFzpwr+GSjLTu8RF8UGpArzR8kvbN 4wcHz0pMAE4ctM2HkSIo9pGrN8MtejCLD/YrUzymb08KkzizdiUSt+ZX3Ha8nz/GhVSe FFfvARNEqMlAyMoqx+mYvQ39vfHAx01IIv/LaL5z/baVH07MzXLhA3eSPQerkEzbn/q7 +ya0CufuqKn+6BReRfBY4pQ/gOrZUyvrzkIWkaQ0fieG225/kHeA2prvtiIqBa03LLNq P4HaV8RnL/vVEARTzjxacvp1Uh0q9KOLSIh4Yi908myXEwboZRvryTy0wfGSxNslw4Sw vQrg== X-Gm-Message-State: AOAM532Tjme1AKFe3JdxcIVZ+2f2LtweKYT5c46YPHxV/vLZnXkeB0BC XQ4FRjUMv/qqLabLNwR2TkHknQ== X-Google-Smtp-Source: ABdhPJwaiSgV+tZ5hmvhOtm8jdHF9XtABJvMUTOdRAbBc6RVzC4fzfwLo42zbd8gTb+8ce0ut/liYg== X-Received: by 2002:a05:6402:430d:b0:42b:fa5:2a4e with SMTP id m13-20020a056402430d00b0042b0fa52a4emr27534042edc.229.1653460766019; Tue, 24 May 2022 23:39:26 -0700 (PDT) Received: from localhost.localdomain ([2001:871:5e:1e9:68e4:2e29:6ced:f071]) by smtp.gmail.com with ESMTPSA id a22-20020a056402237600b0042bcadce588sm267515eda.60.2022.05.24.23.39.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 May 2022 23:39:25 -0700 (PDT) Message-ID: <4225123ef7e892c550452c22257282ff0755ff09.camel@cybertec.at> Subject: Re: postgresql database use a case insensitive collation From: Laurenz Albe To: Dennis , pgsql-admin@lists.postgresql.org Date: Wed, 25 May 2022 08:39:25 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2022-05-25 at 09:19 +0300, Dennis wrote: > How to make configuration my postgresql database use a case insensitive collation? You'd have to define such a collation with CREATE COLLATION and you have to use it in column definitions explicitly, since such a collation cannot be used as database collation. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com