Re: per table random-page-cost?
От | Kevin Grittner |
---|---|
Тема | Re: per table random-page-cost? |
Дата | |
Msg-id | 4ADD7BA6020000250002BB85@gw.wicourts.gov обсуждение исходный текст |
Ответ на | Re: per table random-page-cost? (Greg Smith <gsmith@gregsmith.com>) |
Ответы |
Re: per table random-page-cost?
|
Список | pgsql-hackers |
Greg Smith <gsmith@gregsmith.com> wrote: > The unfortunate reality of accounts receivable is that reports run > to list people who owe one money happen much more often than posting > payments into the system does. How often do you have to print a list of past due accounts? I've generally seen that done weekly or monthly, in the same places that there are many people standing full time in payment windows just to collect money from those lining up to pay. When they bring in a document which identifies the receivable (like, in our case, a traffic or parking ticket), there's no need to look at any older data in the database. Heck, even our case management applications likely follow the 90% to 95% cache hit pattern in counties which aren't fully cached, since there's a lot more activity on court cases filed this year and last year than on cases filed 30 years ago. -Kevin
В списке pgsql-hackers по дате отправления: