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 1rZ6Fs-0024fh-0V for pgsql-general@arkaria.postgresql.org; Sun, 11 Feb 2024 09:36:08 +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 1rZ6Fq-002Tub-Mb for pgsql-general@arkaria.postgresql.org; Sun, 11 Feb 2024 09:36:06 +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 1rZ6Fq-002TuS-8R for pgsql-general@lists.postgresql.org; Sun, 11 Feb 2024 09:36:06 +0000 Received: from mout.gmx.net ([212.227.15.18]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rZ6Fi-006BGR-Mg for pgsql-general@lists.postgresql.org; Sun, 11 Feb 2024 09:36:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=s31663417; t=1707644156; x=1708248956; i=karsten.hilbert@gmx.net; bh=UNIM8ZipXhrtm+uPZtet9DsOsEhgG7JDELdSNO0X31I=; h=X-UI-Sender-Class:Date:From:To:Subject:References:In-Reply-To; b=bdQA7vkImjOQfKMorV4tbCdz9tKli0Rq+n76nAo76pw5Q9JbMzC19pSnvLS1TjuT LGRGAwc5NO+5wObdAYARwOY6dHlML+bCsy6WZ7W/OoUQ+XYbroCmKNY5Tl+CYLufZ ZlBHJhVLmgW++PRcrbP/RH0M6Kp39ysJKRWD8thiLAWUuvIR4oVaUZZg9mp3zYXNs pJo8W1QHpEyuOvkuPR0HmmMfl3pVsAHXsYmN4L1VDHz8+P2XTZNEPSO6+W6+58BiR UChUPQakSSSQ/Xv6axKn0Wbi4aq8OeBQrw4q1f8C08nUq28pZDu27jyNTpMfjxDMM LBeksg0HKRctAD1PTQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from hermes ([88.117.178.2]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MIMbO-1rnPaB43Lo-00EKKb for ; Sun, 11 Feb 2024 10:35:56 +0100 Received: from ncq by hermes with local (Exim 4.96) (envelope-from ) id 1rZ6Fl-0000uU-1m for pgsql-general@lists.postgresql.org; Sun, 11 Feb 2024 10:36:01 +0100 Date: Sun, 11 Feb 2024 10:36:01 +0100 From: Karsten Hilbert To: pgsql-general@lists.postgresql.org Subject: Re: How should we design our tables and indexes Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Ma_X_il-Followup-to: d Re_X_turn-receipt-to: Karsten.Hilbert@gmx.net Di_X_sposition-Notification-To: Karsten.Hilbert@gmx.net X-Confi_X_rm-Reading-To: Karsten.Hilbert@gmx.net X-Pri_X_ority: 2 (High) Sender: X-Provags-ID: V03:K1:mgClfnVQ1CmzXDysrPahfPdppacO+m2HD2X5qorHISHGfYLD0uY ueOh+zuPDUr9hpdIeaJDwmNg6jH9s3j6xzi2WKZhiS7aefjQqFm1qBW6by/rQP4Lq+Lxnwj BertMTDt11C+vitMvjzXafldsQ5uPkkuJYdJSTFLTUoP13FpxJgt3MzBrJlXSSsLZcq7xtJ upYEYbKpcP1OHJkuCDftQ== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:2Mq60aN0+aQ=;PmYl+IRAPuhQ6ec/sHv2m5NOLV7 +5o9D3ddyjRhGFfEea+2sdDzBRVyeTB10oqmxWO0CLFtCazY5MLiHTwN56gIsIvq5E+40+TEs rtpnSiHEMitD5WMnfeSubJbxGVBCxDoYENzcTHAeJ5vbO4vCsTILy49Q/rzQ12DrzxVh7BwQW OC/hx7ZVzPMruYvCEClLtVVuCeIRqhraT48EDW5zXnynqrtKRbwbbdOzc4u4G7ke/0+jU9V6Y AF6BtwkjH1TJpdxXv8eI93DA/jHdlSXMbVNl7il8PVKBMI8ys7hdCZO8vPw+Ww43iy1tlTKsu r/xQtAZTGe47hmTwIToaa9dl+ZHSbHAM1bCRyZ++DxD3e72HZ1eCX3Kt8fpIzDtZkJuzk1klH 1fb/fZlupzJ9o+LW/DRnw5MpiRhhJnDwJNTAnAqY1rfbFY2T3smBTZ9OuvRoJEJVgq9vAZ/Ly 3gYmLd5TmvhYRc6RZIyE19Ldvn0ebi1RA6mSCzEVez7P7s6zHM0XUzYgyXIcubVzyFf3Iuo5F BLEqCw7+9DBFcZsjWaSnFFYeOBtRp0KB3MRnZEa9dqW2AxiZhg66gr81iBRA1sX0EuDSDLsAm 2fiUN9Ekcryee352MKtOat7OtSPZz4Uuv6IOGad/z/azPP1NctiK7IrfHWyLW8due3tPYCs0o USsQwyM3OUEJS2FujfoK4mOKEur2Gcy5n6Ykeb8aNpIuZEMiavvSbRhYHbvwax18y3Xw5/nVf IgnIi6rEQAovMCfDOrH640dGORL2+5VQ+nmMPunQX5hv6rhEbG9Y36Rozy9RYGk96m9rrhqn8 H4fj+Hr411t8ArR408A13lI6zMlNnrIcMSGSgmV4eEqEQ= Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Am Sun, Feb 11, 2024 at 12:53:10PM +0530 schrieb veem v: > >> Pagination is already a hard problem, and does not even make sense wh= en > > combined with "a continuous stream of inserts". What should the user s= ee > > when they click on page 2? > > > > When the user clicks to the second page , it will see the next set of ro= ws > i.e 100 to 200 and next will see 200 to 300 and so on till the result se= t > finishes. Given a continuous stream of inserts "second page" or "next set of rows" is undefined -- if you aim for live data, because interleaving data may have been inserting while the user inspected the first batch of results. A "second page" is only defined in terms of "what the original query returned on the first run". Karsten =2D- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B