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.89) (envelope-from ) id 1hlE09-0003sp-Ue for pgsql-hackers@arkaria.postgresql.org; Wed, 10 Jul 2019 14:55:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hlE08-0006g8-Fj for pgsql-hackers@arkaria.postgresql.org; Wed, 10 Jul 2019 14:55:20 +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 1hlE08-0006cX-2M for pgsql-hackers@lists.postgresql.org; Wed, 10 Jul 2019 14:55:20 +0000 Received: from mail-pl1-x62e.google.com ([2607:f8b0:4864:20::62e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hlE05-0005AW-Qo for pgsql-hackers@postgresql.org; Wed, 10 Jul 2019 14:55:19 +0000 Received: by mail-pl1-x62e.google.com with SMTP id b3so1368037plr.4 for ; Wed, 10 Jul 2019 07:55:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=illuminatedcomputing-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=C7u7+u9Bsa739A7JE4Av7QeM//F7YOmj4K7N1I0uc8k=; b=l7IITLnbsBpcnArLDXMqAgE00Pm/xdj3kR33sYpuR2YuTrvg4hBHOoAzy+6Td5HcxP k/dCLkAcjrCURl/9qmX/8oUvsMEdEG8vIQ2YBK0ulI4EiJBYEOkRLXPFK5mt8SxgCxw3 dtOzVl03p3ZzYVn9bJbYxP5Q220mP+fi8I5xOK8lzv/wQ44rWoYVQvk3RzxW3pRkd0BM sLiVvWsV4Hv6GwLNQG4o1/FoNzTHcswxrysiIdsG/vsjm1AFmPw99r7wzWUus+QiQxPB r/MlByNEeVPIxwVAD8Iv0cKKA++vxqi5cdveIjlZISojfyd/ucCnZzf55f2N2LLPXOEH m25Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=C7u7+u9Bsa739A7JE4Av7QeM//F7YOmj4K7N1I0uc8k=; b=mU8zaPuJmK99GiaAg22ccMsEwSsTNCOaUsOS/8ZqMbic1xECL900r4g7jBdqcYhBk+ wa2yXxNYIDWKB9364polCwXybDk+tCGv5Rn2ez/BSTdlRbS3RaA2Ilycx579TAB4JocC H4TcKC01RbsDIB+WaimRLULf/uRFZWaq/UzQYZRk8gQr3jHUrOZ0e10RuADtwfHHYXGx IRF1m1SsNGAkfd4jcjof7rI/AOgJy+7g+Wku97gCu8NBFO+3x8co2wmvisoq2Ow1sZVN 26Vd9PcJKtD3XfvNTjUrm5jjkbetOiWeLBWp3DHNW9sintGR8yDu0WTVUjP/2gQO4XqT LbkQ== X-Gm-Message-State: APjAAAXBXFRn6pUhtR/AMTdb1HWAeBtYjDIVi9Pm/M3KaB5cqSyMXNfp +Zgyz0DfBbdb5QKOQFs5HzsZks0tkeA= X-Google-Smtp-Source: APXvYqzbpegw1Hj/BaUMWHHcTm3NceUFi9ta7eNJqcxBfPDUG5IXYP2ch+YDCKSldv9OPNrNy9LFmQ== X-Received: by 2002:a17:902:2bc5:: with SMTP id l63mr40557794plb.30.1562770514209; Wed, 10 Jul 2019 07:55:14 -0700 (PDT) Received: from [192.168.2.101] (static-50-53-109-254.bvtn.or.frontiernet.net. [50.53.109.254]) by smtp.googlemail.com with ESMTPSA id j15sm2523339pfr.146.2019.07.10.07.55.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jul 2019 07:55:12 -0700 (PDT) Subject: Re: range_agg To: David Fetter Cc: Jeff Davis , Pgsql Hackers References: <16d71dc8-34cf-5ebd-1ce5-ccd93c0a14f9@illuminatedcomputing.com> <20190709155112.GH24679@fetter.org> <20190710062359.GI24679@fetter.org> From: Paul Jungwirth Message-ID: Date: Wed, 10 Jul 2019 07:55:11 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1 MIME-Version: 1.0 In-Reply-To: <20190710062359.GI24679@fetter.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 7/9/19 11:24 PM, David Fetter wrote: >>> I seem to recall that the usual convention (at least in math) is >>> to use intervals that are generally represented as open on the >>> infinity side, but that might not fit how we do things. >> >> I think it does, unless I'm misunderstanding? > > Oh, I was just wondering about the square bracket on the left side of > [null, 1). It's not super important. Ah, I understand now. Just a typo on my part. Thanks for catching it, and sorry for the confusion! >>> !mr , perhaps? >> >> I like that suggestion. Honestly I'm not sure we even want an inverse, >> but it's so important theoretically we should at least consider >> whether it is appropriate here. Or maybe "inverse" is the wrong word >> for this, or there is a different meaning it should have. > > Jeff's suggestion of ~ for complement is better. Okay, thanks. I like it better too. Yours, -- Paul ~{:-) pj@illuminatedcomputing.com