Hello all,
I sent a similar post to a FreeBSD group, but thought I'd might try here too.
I am completing a box for PostgreSQL server on FreeBSD. Selecting a RAID controller I decided to go
with 3ware SE9650-16, following good opinions about 3ware controllers found on FreeBSD and
PostgreSQL
On 3/20/07, Ireneusz Pluta [EMAIL PROTECTED] wrote:
Hello all,
I sent a similar post to a FreeBSD group, but thought I'd might try here too.
I am completing a box for PostgreSQL server on FreeBSD. Selecting a RAID
controller I decided to go
with 3ware SE9650-16, following good opinions about
On Tue, Mar 20, 2007 at 10:18:45AM -0400, Merlin Moncure wrote:
On 3/20/07, Ireneusz Pluta [EMAIL PROTECTED] wrote:
Hello all,
I sent a similar post to a FreeBSD group, but thought I'd might try here
too.
I am completing a box for PostgreSQL server on FreeBSD. Selecting a RAID
I've got one logging table that is over 330 million rows to store 6
months' worth of data. It consists of two integers and a 4-character
long string. I have one primary key which is the two integers, and
an additional index on the second integer.
I'm planning to use inheritance to split
My question is how small to make each inherited piece? If I do
modulo 10, then each sub-table will be between 32 and 34 million
rows today based on current distribution.
You might try this with various sizes.
I did some testing lateley and found out that insert performance -
even if
Is this technically a good idea to take Promise instead of 3ware or
rather I definitely should insist on 3ware and wait for it?
Use 3Ware they are proven to provide a decent raid controller for
SATA/PATA. Promise on the other hand... not so much.
Joshua D. Drake
Thank you
Ireneusz
On Mar 20, 2007, at 11:20 AM, Heiko W.Rupp wrote:
partition through the master
table abould halfed the speed with 4 partitions and made a 50%
increase for 2 partitions.
Please note: this is not representative in any kind!
I fully intend to build knowledge of the partitions into the insert
On 20-Mar-07, at 9:23 AM, Ireneusz Pluta wrote:
Hello all,
I sent a similar post to a FreeBSD group, but thought I'd might try
here too.
I am completing a box for PostgreSQL server on FreeBSD. Selecting a
RAID controller I decided to go with 3ware SE9650-16, following
good opinions
On 20-Mar-07, at 1:53 PM, Benjamin Arai wrote:
This is a little biased but I would stay away from areca only
because they have fans on the card. At some point down the line
that card is going to die. When it does there is really no telling
what it will do to your data. I personally use
At 02:08 PM 3/20/2007, Dave Cramer wrote:
On 20-Mar-07, at 1:53 PM, Benjamin Arai wrote:
This is a little biased but I would stay away from areca only
because they have fans on the card. At some point down the line
that card is going to die. When it does there is really no telling
what it
After upgrading to 8.2.3 INSERTs and UPDATEs on one of my tables became
incredibly slow. I traced the problem to one of my triggers that calls
one of my defined functions (that is IMMUTABLE). If I inline the
function instead of calling it the runtime for my test update drops from
10261.234
Joseph S jks@selectacast.net writes:
After upgrading to 8.2.3 INSERTs and UPDATEs on one of my tables became
incredibly slow. I traced the problem to one of my triggers that calls
one of my defined functions (that is IMMUTABLE). If I inline the
function instead of calling it the runtime
I've found that it would be helpful to be able to tell how busy my
dedicated PG server is ( Linux 2.6 kernel, v8.0.3 currently ) before
pounding it with some OLAP-type queries. Specifically, I have a
multi-threaded client program that needs to run several thousand
sequential queries. I broke
Dan Harris wrote:
I've found that it would be helpful to be able to tell how busy my
dedicated PG server is ...
I have seen some other nice back-end things exposed through PG functions
( e.g. database size on disk ) and wondered if there was anything
applicable to this.
I'd write a simple
(forgot to send to list)
Dan Harris wrote:
architecture of the server hardware. It would be very nice if I could
check the load of the server at certain intervals to throttle the
number of concurrent queries and mitigate load problems when other
processes might be already inducing a
Dan Harris wrote:
I've found that it would be helpful to be able to tell how busy my
dedicated PG server is ( Linux 2.6 kernel, v8.0.3 currently ) before
pounding it with some OLAP-type queries.
..snip
Thank you all for your great ideas! I'm going to try the perl function
as that seems
Dan
Use the following plperlu function
create or replace function LoadAVG()
returns record
as
$$
use Sys::Statistics::Linux::LoadAVG;
my $lxs = new Sys::Statistics::Linux::LoadAVG;
my $stats = $lxs-get;
return $stats;
$$
language plperlu;
select * from LoadAVg() as (avg_1 float,avg_5
17 matches
Mail list logo
