From: | Toni Alfirević <toni(dot)alfirevic(at)gmail(dot)com> |
---|---|
To: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
Cc: | pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: DB design advice |
Date: | 2013-06-07 06:43:02 |
Message-ID: | C8800CE0-51C9-45B9-9C01-055424BFF2C6@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On 7. 6. 2013., at 07:39, Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> wrote:
> On Thu, Jun 6, 2013 at 2:29 AM, Toni Alfirević <toni(dot)alfirevic(at)gmail(dot)com> wrote:
>> And app should allow user to search trough his logs filtered by one or more
>> tags and time interval. Here is one more constraint, since those messages
>
> Is it supposed to return all the data from this interval at once, or
> to be implemented like a kind of pagination/slider, that gets a
> limited amount of entries since the beginning of the interval, and
> then, after user requested more, it gets entries that are after the
> last one from the previous bunch, and so on?
Hi Sergey,
It will most likely return subsets of data just like you said (pagination).
But there will be a situation where all data will need to be analyzed for, let's call it', a report. On the other hands those reports are not that sensitive when it comes to performance. It won't be an issue if it takes a minute, two or three to generate it.
From | Date | Subject | |
---|---|---|---|
Next Message | Aditya Rastogi | 2013-06-08 05:24:42 | PostgreSQL 8.3.6 creating empty log files. |
Previous Message | Sergey Konoplev | 2013-06-07 05:39:24 | Re: DB design advice |