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 1qvj9U-006wcW-26 for pgsql-hackers@arkaria.postgresql.org; Wed, 25 Oct 2023 19:02:48 +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 1qvj9S-007Hny-MH for pgsql-hackers@arkaria.postgresql.org; Wed, 25 Oct 2023 19:02:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvj9S-007Hnq-Cj for pgsql-hackers@lists.postgresql.org; Wed, 25 Oct 2023 19:02:46 +0000 Received: from mail-pf1-x42a.google.com ([2607:f8b0:4864:20::42a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qvj9P-002llr-Ru for pgsql-hackers@lists.postgresql.org; Wed, 25 Oct 2023 19:02:45 +0000 Received: by mail-pf1-x42a.google.com with SMTP id d2e1a72fcca58-6934202b8bdso65849b3a.1 for ; Wed, 25 Oct 2023 12:02:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20230601.gappssmtp.com; s=20230601; t=1698260561; x=1698865361; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=jo2/gwvk1n1Fi0m1/+M2DuW/hd9rqhS0UbKCkrFYEZA=; b=L0MeQqxw3uB8RnEmQVyiQtdroWF9NkldSqfsp9d4tp4Ns/r49/xgp/YkticP7wHAOI 5Lwx70zATx1dp3JRnYT0xEo1wmilwFbRoj8hxJmwjL1mNWjzgVXOUbiPVi8spt7XMRoM vPh5gD9fDUdB7hAcR0DaF/NoeZFxqPT+SjUj9eNZ+6pYflCjkreQaH10D9IcrE7pSrU9 dS+JodvJe/sYWbUaGCscrQ7Cq+OzFniOe2/MT/Bmp6xtBoI4qh/lPxbYandsUH3rsgBK VMwjhVfq1cf4ysg5n33s/3a907oaZQPbYDmaO5myTR4pGyV7fpw8EBlFnErcgKUS2D56 FV9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698260561; x=1698865361; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=jo2/gwvk1n1Fi0m1/+M2DuW/hd9rqhS0UbKCkrFYEZA=; b=u9tkpAWJDaPEUTrvwuRxK/HyE+/Nq53S9dBm7HA5VPQO6Zbn2p0MMS+pqHTGZOut23 +pAatwnXObP4sZKgfFhuLSVdFrPURmsS2UgVijYwxGfIPVVZCvxsw+k8QpUnY6f/gZz3 NBNJBEwMDaamDNOSYI9oKQ7815+Ho8Le4EjhOS43EbQqd0kQ3mMs4YND3wDIpoX4Qemv bJGdvOawlpuZtWO7qyZZu5o5vAEVTcLlU17MWG8uW/6Poy05nCNu+grKtigyqbaPK3iG EOBwzP3zmIN5Fl1pggxjfkSD3f3bSZLAZ0BIgKAaM8u20xLfL+2jp3iHORn4+2QCWQLf ULoQ== X-Gm-Message-State: AOJu0YyWhQXYECM1ZykNhcj1ny6v+OhxmLry7xVVvCvdxXJ70r1FjxwE KLRGFejx97vqYF3Hsu9F+iil1w== X-Google-Smtp-Source: AGHT+IGjpN1A+fDu7yDhOlV/5UE/GBjmMtGHLfgxTWxcxiCytD9lhGNzp8dbfhSjSiMuuq+Xjzel/g== X-Received: by 2002:a05:6a21:4842:b0:16a:4480:647f with SMTP id au2-20020a056a21484200b0016a4480647fmr6430661pzc.19.1698260561122; Wed, 25 Oct 2023 12:02:41 -0700 (PDT) Received: from jeff-laptop.lan (c-76-102-242-158.hsd1.ca.comcast.net. [76.102.242.158]) by smtp.gmail.com with ESMTPSA id k17-20020aa79d11000000b006933866f49dsm9985810pfp.19.2023.10.25.12.02.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Oct 2023 12:02:40 -0700 (PDT) Message-ID: <02cdee30c37e925eb168293a59bb5a432dd5f091.camel@j-davis.com> Subject: Re: Custom tstzrange with importance factored in From: Jeff Davis To: "Rares Pop (Treelet)" , pgsql-hackers@lists.postgresql.org Date: Wed, 25 Oct 2023 12:02:40 -0700 In-Reply-To: <8CB43014-79BC-4FA4-9838-A17313D525F9@treelet.net> References: <8CB43014-79BC-4FA4-9838-A17313D525F9@treelet.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4-0ubuntu2 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 2023-10-06 at 16:55 +0300, Rares Pop (Treelet) wrote: > I essentially want to be able to aggregate multiple tstzranges - each > range with its own importance. The aggregation would be like a a > join/intersect where ranges with higher importance override the ones > with lower importance. It may be possible without a new data type. Can you describe the semantics more precisely? Regards, Jeff Davis