pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: pgsql-general@lists.postgresql.org
Subject: Re: How should we design our tables and indexes
Date: Sun, 11 Feb 2024 10:36:01 +0100
Message-ID: <ZciVAQKU9-mCH3Ua@hermes.hilbert.loc> (raw)
In-Reply-To: <CAB+=1TV=bAokrJhM9JjqfLTpemyr3SwbJLTFpXmfggtcw2qKCg@mail.gmail.com>
References: <CAB+=1TXnsSW384gsJxOFvzJt=+coUWh5my39mkHwZEEWPFCsWQ@mail.gmail.com>
	<CAKAnmmL=x_3Ga_aBa1UQfHjcCikV7SJX5iM9n4b0bb76cgZVyQ@mail.gmail.com>
	<CAB+=1TV=bAokrJhM9JjqfLTpemyr3SwbJLTFpXmfggtcw2qKCg@mail.gmail.com>

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 when
> > combined with "a continuous stream of inserts". What should the user see
> > when they click on page 2?
> >
>
> When the user clicks to the second page , it will see the next set of rows
> i.e 100 to 200 and next will see 200 to 300 and so on till the result set
> 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
--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B





view thread (11+ messages)  latest in thread

Message-ID: <ZciVAQKU9-mCH3Ua@hermes.hilbert.loc>
Permalink:  ../ZciVAQKU9-mCH3Ua@hermes.hilbert.loc/
Also on:    postgresql.org/message-id/ZciVAQKU9-mCH3Ua@hermes.hilbert.loc

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: Karsten.Hilbert@gmx.net
  Subject: Re: How should we design our tables and indexes
  In-Reply-To: <ZciVAQKU9-mCH3Ua@hermes.hilbert.loc>
  References: <CAB+=1TXnsSW384gsJxOFvzJt=+coUWh5my39mkHwZEEWPFCsWQ@mail.gmail.com> <CAKAnmmL=x_3Ga_aBa1UQfHjcCikV7SJX5iM9n4b0bb76cgZVyQ@mail.gmail.com> <CAB+=1TV=bAokrJhM9JjqfLTpemyr3SwbJLTFpXmfggtcw2qKCg@mail.gmail.com> <ZciVAQKU9-mCH3Ua@hermes.hilbert.loc>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox