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 1r0L4o-0055vO-Mv for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Nov 2023 12:21:02 +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 1r0L4m-008840-UZ for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Nov 2023 12:21:00 +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 1r0L4m-00883r-IJ for pgsql-hackers@lists.postgresql.org; Tue, 07 Nov 2023 12:21:00 +0000 Received: from mail-lj1-x22e.google.com ([2a00:1450:4864:20::22e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1r0L4f-004Oac-7Q for pgsql-hackers@lists.postgresql.org; Tue, 07 Nov 2023 12:20:58 +0000 Received: by mail-lj1-x22e.google.com with SMTP id 38308e7fff4ca-2c594196344so74391001fa.3 for ; Tue, 07 Nov 2023 04:20:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699359651; x=1699964451; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Mh43HRZYhd6ueuInWlOiw0Im33jfu8ZQOyj1wrGkKnU=; b=hKPAYWa/+MQ49kbVDwXOOoszQdRhMz8GTZexXSbC+6HzyJAKWxl+9adtYzpOeWojf8 G+sy0tWVAFzmcOi3fdaZvAQLCnI6eIj+BlJvlLVhs8P8lmj78k35qhcsmSvfl0IKDFnP INM0ZvLXOL03qdCFD+fArwieUuq+UXCzAteJDWTr51KAwGLnpAeJDB5JrmfEMEdXIkah MuQ7QLnv1f/ZAAJNk3BmAJKecq1NH21bRUP5wc1k6J0OGpKdE0zTITMAlKMuGb1fr5np vNfTXdbGlWS+wH0ZRL6oLcGnx4MC5OM6GcrJEGrp9TgjqdnHDsZuyIAAZiWW13cjbZe0 R44Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699359651; x=1699964451; h=content-transfer-encoding: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=Mh43HRZYhd6ueuInWlOiw0Im33jfu8ZQOyj1wrGkKnU=; b=GbBry8I/TbnuPsZw9wC70GQM1hwSkeT9c9j/l0he9POdRujfnIl3eZLePDGotHwzVd Oq6cL0/Y4rPPElKJJu/52bdlMPYiD3CpFMt8yIdWB0h50vX9lPeQMSRu3wleB39sFgMK F2TlgRoJIL09vEXdYrnziGmNaKAqeXIGloiQEGLBBXSkKG3IpFqiWs+nQKS+4Xs9Y4be eitJfop9Cp+7GAzRSJEt52clZMJ+BrK7h0UwB+3XuDMR6gGt3ssMIWSp0oEth6whkof9 yjdR7FAK8ygovomiCVTYsEE+6cD1wnf4wbmuOxr+cAj3Gk1TJdvCnKXqQx5n5m9DMnvl OTow== X-Gm-Message-State: AOJu0YzI3hTMxpA57sVHEjQ3wvEQ4iY33pr4LZjiWmIA01urLXxlVTLf /rswhbWqdAxo/Obl8DkKfwnL+BIQcGwugSCINKM= X-Google-Smtp-Source: AGHT+IEfXz8fIkCaCUGB063eR4mzJl8hnuOwgdq9QcfxHtPuaqTXM3hIGMPSKKRjvAFJ3zBI1eQxtHuX3HNciMp1VoQ= X-Received: by 2002:a05:651c:10:b0:2c5:2126:127a with SMTP id n16-20020a05651c001000b002c52126127amr23901334lja.17.1699359651166; Tue, 07 Nov 2023 04:20:51 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Matthias van de Meent Date: Tue, 7 Nov 2023 13:20:39 +0100 Message-ID: Subject: Re: Optimizing nbtree ScalarArrayOp execution, allowing multi-column ordered scans, skip scan To: Peter Geoghegan Cc: PostgreSQL Hackers , Tom Lane , Tomas Vondra , Jeff Davis , benoit , Alexander Korotkov Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 7 Nov 2023 at 00:03, Peter Geoghegan wrote: > > On Mon, Nov 6, 2023 at 1:28=E2=80=AFPM Matthias van de Meent > wrote: > > I'm planning on reviewing this patch tomorrow, but in an initial scan > > through the patch I noticed there's little information about how the > > array keys state machine works in this new design. Do you have a more > > toplevel description of the full state machine used in the new design? > > This is an excellent question. You're entirely right: there isn't > enough information about the design of the state machine. > > I should be able to post v6 later this week. My current plan is to > commit the other nbtree patch first (the backwards scan "boundary > cases" one from the ongoing CF) -- since I saw your review earlier > today. I think that you should probably wait for this v6 before > starting your review. Okay, thanks for the update, then I'll wait for v6 to be posted. Kind regards, Matthias van de Meent Neon (https://neon.tech)