Re: pgarchives new design review

On Sat, 6 Aug 2022 at 16:37, Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> A configurable like that could be done in client side javascript with a
> browser cookie if really wanted though -- as long as All is the
> default, meaning all the data is sent to the browser, local pagination
> can be done in the browser.
>

Yeah right. I am doing the same thing. All the data is being loaded only
once, and all the pagination is happening on the client side. Also, I
changed the default pagination value to *All* and changed the table's
structure to make it a bit more compact.

http://140.211.168.145:88/list/pgsql-hackers/2022-07/

//Sahil

On Sat, 6 Aug 2022 at 16:37, Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> On Fri, Aug 5, 2022 at 12:52 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> >
> > > On 5 Aug 2022, at 12:25, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
> wrote:
> >
> > > In my opinion, the list of messages shown for a period of time has to
> be
> > > a continuum of *all* messages in that period, without these paging
> breaks.
> > >
> > > I prefer to scroll.
> >
> > Using the archives a fair bit as well, I agree with that. I don't mind
> there
> > being an option for paging but I would prefer if "All" was the default
> or if
> > it's saved as a setting in my profile such that I get it when being
> logged in.
>
> Right now the archives operate entirely without logged in users for
> browsing. We do *not* want to change that, because we use that to
> build some geographical redundancy in the caching for example. A
> configurable like that could be done in client side javascript with a
> browser cookie if really wanted though -- as long as All is the
> default, meaning all the data is sent to the browser, local pagination
> can be done in the browser.
>
> //Magnus
>