We have a 4x 2.4ghz Opteron box w/ 8 gigs of ram running a very busy pg
8.1.4 server. Upon startup we see around 15-20 "statistics buffer is
full" messages and they repeat at random times throughout the day.
During peak times the box sometimes seems to grind to a halt. Any thoughts?
- E
-
= on
#stats_reset_on_server_start = off
- E
Joshua D. Drake wrote:
Eci Souji wrote:
We have a 4x 2.4ghz Opteron box w/ 8 gigs of ram running a very busy
pg 8.1.4 server. Upon startup we see around 15-20 "statistics buffer
is full" messages and they repeat at random times throughout the da
Hi, I was wondering if anyone had any experience with this type of
setup and could share what they've learned.
Basically we've got several different "states" that an item can be in.
From what I've seen the way many places seem to deal with them is
something along the lines of making bool values t
Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2006-05-28 16:13:20 -0400:
Basically we've got several different "states" that an item can be in.
From what I've seen the way many places seem to deal with them is
something along the lines of making bool values that act as
switches...
Ex:
table ite
Chris wrote:
Eci Souji wrote:
Hi, I was wondering if anyone had any experience with this type of
setup and could share what they've learned.
Basically we've got several different "states" that an item can be in.
From what I've seen the way many places seem to de
Perhaps it was in reference to Hyrule Rupees? :)
http://en.wikipedia.org/wiki/Rupee_(Legend_of_Zelda)
Ben wrote:
...and as I learned the last time I returned from India, no bank
outside of India will exchange rupees, because it's technically illegal
to take rupees outside the country. So u
Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2006-05-29 08:10:43 -0400:
Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2006-05-28 16:13:20 -0400:
Basically we've got several different "states" that an item can be in.
From what I've seen the way many places seem to deal with them is
som
So we've got a table called "books" and we want to build records of how
often each book is accessed and when. How would you store such
information so that it wouldn't become a huge unmanageable table?
Before I go out trying to plan something like this I figured I'd ask and
see if anyone had an
"
within the 8.1 release notes / the postgresql documentation.
Harald
On 7/16/06, *Eci Souji* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
So we've got a table called "books" and we want to build records of how
often each book is accessed and w
Hash: SHA1
Eci Souji wrote:
What if instead of book checkouts we were looking at how often a book
was referenced? In which case we're talking multiple times an hour, and
we could easily have each book requiring hundreds of thousands of rows.
Multiply that by hundreds of thousands of books
10 matches
Mail list logo
