From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Sahil Harpal <sahilharpal1234(at)gmail(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: pgarchives new design review |
Date: | 2022-08-06 11:07:33 |
Message-ID: | CABUevEx42AcXBTmT8RpFWYjiXOYJm0fJ0C3WhJrG2PUBU466yA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2022-08-06 11:22:38 | Re: Weird mangling of a commit log entry in gitweb summary |
Previous Message | Julien Rouhaud | 2022-08-06 08:18:41 | Re: pgarchives new design review |