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 1so9sT-008jV8-CC for pgsql-general@arkaria.postgresql.org; Tue, 10 Sep 2024 23:02:30 +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 1so9sT-0045ZE-3r for pgsql-general@arkaria.postgresql.org; Tue, 10 Sep 2024 23:02:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1so9sS-0045Z6-Nj for pgsql-general@lists.postgresql.org; Tue, 10 Sep 2024 23:02:28 +0000 Received: from mail-lf1-x12c.google.com ([2a00:1450:4864:20::12c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1so9sP-000XPk-W6 for pgsql-general@postgresql.org; Tue, 10 Sep 2024 23:02:27 +0000 Received: by mail-lf1-x12c.google.com with SMTP id 2adb3069b0e04-5365b6bd901so5403825e87.2 for ; Tue, 10 Sep 2024 16:02:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726009344; x=1726614144; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=W8JWC2NhkMoJf7wmzypya6HX+DHhaYpfOozyLpEo3vc=; b=WPYAUmXQKQOfMqCasfJttS+iYEaD1co4i8YUsxfnHOl4KCFuspXDcsHkTO6FRkqH+s nr3nSS6TfLcZFrJUztX78W4Of+K/uodjj4mpSrA8vuaAgdthBFt4Myq0x9nV6IfjdGwh +l7U4GCEd4cw32akE8fAPL+V7VSkO10wl60e0PMNVKf8ZXyvL+Uo5fSY4N+r3udq0hZh fiFUvqPfHocu8o/BQ3XCK8DbiFcqt4ys3TXLwsJ8UI9JGlSaJwmYgDSG2H6CbbzjUdVr mZrn4LC0yWuG9xYUkqk/jA74m75Es0voS9oaaXaJuRqFMgC3Zk1jPOfpRhfvs+4Z9M3K k7Tg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726009344; x=1726614144; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=W8JWC2NhkMoJf7wmzypya6HX+DHhaYpfOozyLpEo3vc=; b=KkpkgWYN/Sd+BxB3BgWm5dIR+JwvoWy3rp2FZsNO+7hMWAQskvxWNp0J1x3837+a9n 75FhTMwGy5hY2siwmktFxsVpHMIInZXKk15B00i3rr9PCbLbVMgoPaU+9gg9/kDlxBOk 9K/G5ADZ9KYm8Xu80fprjGotdTBGrOasoJbmv0oPzL2o0qQsjv5IWdVHnHgMoNTMc/p/ Ksg1YWDNT2KNuvYm9bf/7U/KLZ02FadKfLb51cKJHx2Y5QdIx74ycGeJYtvEM3YB6qIZ 3+Yb6VqbXxYxo4h7pIf7SmONTswqJvqrbQHR514wNepfsPRP5DxHCwG6HI9CPmbdtC3x OgUQ== X-Forwarded-Encrypted: i=1; AJvYcCWK/TLTm5CSBDyu+i+hCaargjTrbdaU0l5qYTug0pH4ns93eQmjimDE9xfR9ocDkSIU7IlT5x3BDML7wt0A@postgresql.org X-Gm-Message-State: AOJu0Yw0OszGL3/j0NU03/t5Dnku7bXYhoWi49wDVFpFK0H+kPhLfhRp FTOmaVAFxcbgiCoHV2yCOxEc308jVN3s081xY969SEiQyWLlFrH+Ky+U85EKxHszOUXQS0mQDRd AnAq47DbYn9yjSNKwkVz7io7o1ZHYkw== X-Google-Smtp-Source: AGHT+IFCSP0wmAZxP99eFt1V90XU18WB1fOV176VaHg36PddDZ6xy5F8dJBXAK5tgM9m07QgiL9GPmURjKMQRwnAoHQ= X-Received: by 2002:a05:6512:12c1:b0:51a:f689:b4df with SMTP id 2adb3069b0e04-536588093femr8997292e87.44.1726009343730; Tue, 10 Sep 2024 16:02:23 -0700 (PDT) MIME-Version: 1.0 References: <2FAC43EB-7E04-476A-BEBE-39CDBCA0EDCC@thebuild.com> In-Reply-To: From: David Rowley Date: Wed, 11 Sep 2024 11:02:11 +1200 Message-ID: Subject: Re: Overlapping values (?) in multi-column partitioned tables To: Laurenz Albe Cc: Christophe Pettus , pgsql-general Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 11 Sept 2024 at 10:57, Laurenz Albe wrote: > You should specify the upper bound as ('2023-12-31 23:59:59.999999', MAXVALUE). Or maybe do multi-level partitioning. (it seems strange to always have MINVALUE and MAXVALUE as the range. I'm guessing that was just an example.) David