Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jEGG6-0001s0-45 for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Mar 2020 17:44:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jEGG4-0004DK-QO for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Mar 2020 17:44:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jEGG4-0004DD-F1 for pgsql-hackers@lists.postgresql.org; Tue, 17 Mar 2020 17:44:04 +0000 Received: from mail-lj1-x22e.google.com ([2a00:1450:4864:20::22e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jEGFy-0000M2-48 for pgsql-hackers@postgresql.org; Tue, 17 Mar 2020 17:44:04 +0000 Received: by mail-lj1-x22e.google.com with SMTP id s13so23932476ljm.1 for ; Tue, 17 Mar 2020 10:43:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=BlUGLnM1mKrDsvCly1obp/fZHFtlk9WWhtpa8ONj4w4=; b=qoB89uyva+FtyBbMhIUQre6ezeii4ipaUmosDlKelsh7Fyzvvn2BglXhsUs3kst3eK GmkFEakQEz6JRMQHclL9NWhFjMTpW2dIInjiH0zx7qq04t33a7bQqJsi+0BbMXaDeycy 09KM8OhIU4YQ552RVq9wvLIgpvrpuezC9oqg/IEMLEzx43568PymQQ3qwxmpCWI/rz41 M3LkekPuh2hVJXQXzIlph6MUYlkVpQkpvaaWalqpqvYOPBzBi1oxN4InySELKfXn3/Eo aqfce8vPCkgdRDp/uGjWTqwStt2Y/1DrPxVvaH8ngIq3dx7y0RGMcWHC1R/s92vCaF2r Bvnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=BlUGLnM1mKrDsvCly1obp/fZHFtlk9WWhtpa8ONj4w4=; b=ADqZrqgJIIlWGZp2ebI0abVsg20MhmPzWE7HKDDy3l/dL3ZJsbuqJo+A9O1LzPXbi1 +SNp/7rIucsnWH5H47OweBOL5Ct2P3xAsIyAzMmp0or6Kz9HNWnWoo37S8gWutv/ZVAC KPSErox9E05H0hnRPtIAiGYTHILGVrYf91TB49yM0mRQBjzWoKXHKenFizxxcZ9Yl1TJ CaxEk8Hc+gveGf6DOETT62R+8cL+cfCU2GpfvfiNUZ1HPFjRdbYuxbfmhETbwd5uPq4w F+ELcA2M4FHZtytdoR/ZTi0HblkDCboyqZmfCIvtZpj3z2LBvC975QQBP48CnEZrQs5N 32QQ== X-Gm-Message-State: ANhLgQ2VEj31EU7SI7yOig9713rdtKpARel5pbSBrnv0LULITVYUHqxt q7wE2WbdA/ZlL/3TtfGrG3U= X-Google-Smtp-Source: ADFU+vsMu6L7eogKDygW2cv+cKtzoTaRP3Mfa/Yd03qZkcJ90U1SWdZh3GLqESP5hxX2YhkGRugP6Q== X-Received: by 2002:a2e:3a01:: with SMTP id h1mr3443075lja.161.1584467036781; Tue, 17 Mar 2020 10:43:56 -0700 (PDT) Received: from nol (82-64-124-11.subs.proxad.net. [82.64.124.11]) by smtp.gmail.com with ESMTPSA id v200sm3004000lfa.48.2020.03.17.10.43.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Mar 2020 10:43:56 -0700 (PDT) Date: Tue, 17 Mar 2020 18:43:51 +0100 From: Julien Rouhaud To: Christoph Berg , Peter Eisentraut , Michael Paquier , Thomas Munro , Robert Haas , Laurenz Albe , Douglas Doole , Pg Hackers Subject: Re: Collation versioning Message-ID: <20200317174351.GB63950@nol> References: <20200311084427.GA12358@nol> <20200312140026.GA1689@nol> <20200316075738.GE2331@paquier.xyz> <20200316140520.GA21497@nol> <20200317063749.GF2206@paquier.xyz> <20200317071928.psjiklzvkgqpl3dd@nol> <20200317104234.GA89737@nol> <20200317163147.GA1337480@msg.df7cb.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200317163147.GA1337480@msg.df7cb.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, Mar 17, 2020 at 05:31:47PM +0100, Christoph Berg wrote: > Re: Peter Eisentraut 2020-03-17 > > Did we discuss the regcollation type? In the current patch set, it's only > > used in two places in a new regression test, where it can easily be replaced > > by a join. Do we need it? I originally wrote it for a previous version of the patchset, to shorten the pg_dump query, but that went out when I replaced the DDL command with native functions instead. It didn't seem to hurt to keep it, so I relied on it in the regression tests. > > I realize we've been adding new reg* types lately; I'm not sure what the > > current idea is on that. > > Not sure if that's the case there, but reg* typecasts are very handy > when used interactively in ad-hoc queries. +1. I'm obviously biased, but I find it quite useful when querying pg_depend, which may become more frequent once we start generating warnings about possibly corrupted indexes.