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 1m2oVQ-0000kC-OJ for pgsql-admin@arkaria.postgresql.org; Mon, 12 Jul 2021 05:29:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m2oVP-0002Rv-NH for pgsql-admin@arkaria.postgresql.org; Mon, 12 Jul 2021 05:29:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m2oVP-0002QA-AA for pgsql-admin@lists.postgresql.org; Mon, 12 Jul 2021 05:29:23 +0000 Received: from mail-wr1-x42f.google.com ([2a00:1450:4864:20::42f]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1m2oVI-00047e-OZ for pgsql-admin@lists.postgresql.org; Mon, 12 Jul 2021 05:29:22 +0000 Received: by mail-wr1-x42f.google.com with SMTP id m2so12732624wrq.2 for ; Sun, 11 Jul 2021 22:29:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=RTzC3eTP4vMHgsLXpB56BNpOM+m0AQNRM0KKSYMKyg8=; b=yznGAhndquTxIMIYvZ+rI3RFhvXTEzVOcEnzKxcywPlfXXJG+pxU/R7bwkfCj7GMa+ 3opgykya9ZQRCn7FkfCMgsjY/3M97gU7JfbRJc3QlPI4Uo6t3v6qDAVmYD5AD0EMadQr sLX7EwPseyyKuCFZnHojSnyvrGzU4iBZjzSPxAYHnDXPhTNAPKMJFrkQx2MSMFFY14W/ b/nHkwT8IPJVfTf5urxpCCna+ZCns7VxR+NyCuURI2IBqEjiz3iuQnQGW9dIOup4si9c CEBRU7hf98f+N4uFt9eYSstKsMF3ZE2qKcN85HCBDYUxFTYPddnkyBZm9aK9IA+U/XLD XW7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=RTzC3eTP4vMHgsLXpB56BNpOM+m0AQNRM0KKSYMKyg8=; b=IvJ9ZVQ9TGu+KIhVz8plpOvj00FrQ+dk2T4hgbV2DiLRDkFjaddc4BuX2cOXmGgWVe Wd7uq3OWUTLmoT2MFZMvEbEnDgBjEUrgZZ10eDTAoidlP6HqbLLh9uqZ38BB22j647RN S+qyoBoMY5Gt42IKslYpKGEk51hohUNiZE4V7fc9XIO+SD4I1MUNEtbQlYk+rP3eatd+ s0j4s1JVm05ZihpqvVmAf1MDjEb2h3mapbSVCacYbvd0I8iR0LMZldafQ995iOtVogYl /ey+XXdET33Gu5XFkmjQrhGZLb1aIQ0zPNJ8LI05/lPEVNOTlV2NZfwKjB+lWFu/XNqP c9bQ== X-Gm-Message-State: AOAM530QUTkV7BDoqd4w4SDg4VhAlOEn+39tRaBb/sEWYcJ+wx2pD9Jd Sg9G5zDp6VoONIPJ/hAiyTYTi1Z8GXN5bQ== X-Google-Smtp-Source: ABdhPJx9W86TtB7RGc9H4nGlq//1do63S9VF/WGi8c8Gw/uu+jdrPDsO62aqbDZIKKcDEmtFA6E1eA== X-Received: by 2002:a5d:4402:: with SMTP id z2mr8910644wrq.44.1626067755113; Sun, 11 Jul 2021 22:29:15 -0700 (PDT) Received: from localhost.localdomain (217-149-171-247.nat.highway.telekom.at. [217.149.171.247]) by smtp.gmail.com with ESMTPSA id i15sm14083903wro.3.2021.07.11.22.29.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 11 Jul 2021 22:29:14 -0700 (PDT) Message-ID: <1897c8dce7fd6974116c935a50270b33fac09461.camel@cybertec.at> Subject: Re: Lc_collate & lc_type? whitespace and nbsp unique index... From: Laurenz Albe To: Ilmir Mulyukov , pgsql-admin@lists.postgresql.org Date: Mon, 12 Jul 2021 07:29:14 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 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 Mon, 2021-07-12 at 11:24 +0600, Ilmir Mulyukov wrote: > I have lc_collate and lc_ctype ru_RU.UTF-8. > And have two similar value column in different rows. > Different is that in one string have whitespace symbol, but another non breakable whitespace symbol. > For example: > Something(whitespace)wrong > Something(non breakable space)wrong > > And then when I try to create unique index I catch the error - can not insert duplicate key in row object. > That means that the two rows are the same. > > Are there any settings in postgresql that can differentiate this two symbols I find that hard to believe. Can you provide SQL statements that reproduce the problem? Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com