smiley2211 wrote:
Hello all,
I am a bit confused...I have a database which was performing very POORLY
selecting from a view (posted earlier) on one server but extremely fast on
another server...
I just backed up the database from the FAST server and loaded to the SLOW
server and it ran just as
UPS does not protect against the tech behind the rack unplugging the
power cable, or an accidental power cycle from exercising the wrong
switch. :) Both are probably more common causes of failure than a total
power outage.
Erik Myllymaki wrote:
I have been in discussion with 3ware support and
AFAIK there are no licensing costs for solaris, unless you are talking
about a software support agreement, which is not required.
Juan Casero wrote:
I just sent my boss an email asking him for a Sun v20z with dual 2.2 Ghz
opterons, 2 Gigs of RAM and RAID 1. I would have liked a better ser
I think the T-3 RAID at least breaks some of these rules -- I've got 2
T-3's, 1 configured as RAID-10 and the other as RAID5, and they both
seem to perform about the same. I use RAID5 with a hot spare, so it's
using 8 spindles.
I got a lot of performance improvement out of mount the fs noatim
Here's the answer for you from the jdbc list:
Alvin Hung wrote:
Currently, 8.0.2 / JDBC 8.0-310, log_min_duration_statement does not
work with JDBC. Nothing will get logged. This makes it very
difficult to tune a java application. Can you tell me when will this
be fixed? Thanks.
This i
hmm, yea maybe -- we are using the 7.4 driver with 8.0.x db.
Dennis wrote:
Tom Arthurs wrote:
we are using jdbc -- the "log_min_duration_statement = 3000 "
statement works fine for me. Looks like there's no other work around
for the bug(?). Not sure since I have no intere
055.php
But I can't find anywhere where someone has fixed it.
Am I the only one accessing postgres through JDBC?
-Brent
--- Tom Arthurs <[EMAIL PROTECTED]> wrote:
I have this in my postgresql.conf file and it works
fine (set the min to
whatever you want to log)
log_min_duration_s
I have this in my postgresql.conf file and it works fine (set the min to
whatever you want to log)
log_min_duration_statement = 3000 # -1 is disabled, in milliseconds.
Another setting that might get what you want:
#log_duration = false
uncomment and change to true.
From the docs:
(http://www
I just puhsd 8.0.3 to production on Sunday, and haven't had a time to
really monitor it under load, so I can't tell if it's helped the context
switch problem yet or not.
Neil Conway wrote:
Tom Arthurs wrote:
Yes, shared buffers in postgres are not used for caching
Sh
ching.
Donald Courtney wrote:
Tom Arthurs wrote:
According to my research, you only need a 64 bit image if you are
going to be doing intensive floating point operations (which most db
servers don't do). Some benchmarking results I've found on the
internet indicate that 64 bit executable
According to my research, you only need a 64 bit image if you are going
to be doing intensive floating point operations (which most db servers
don't do). Some benchmarking results I've found on the internet
indicate that 64 bit executables can be slower than 32 bit versions.
I've been running
On the context switching issue, we've found that this setting in /etc/system
helps:
set rechoose_interval=30
this sets the minimum time that a process is eligible to be switched to another
cpu. (the default is 3).
You can monitor context switching with the cs column in vmstat. We've found
that
Hi, All
I'm trying to tune a software RAID 0 (striped) on a solaris 9, sparc box.
Currently I'm using a raid 1 (mirrored) array on two discs for the data area,
and I put in 4 new drives last night (all are f-cal). On the new array I have
a width of 4, and used the default interleave factor of 3
Hi, Paul
Josh helped my company with this issue -- PG doesn't use shared memory like
Oracle, it depends more on the OS buffers. Making shared mem
too large a fraction is disasterous and seriously impact performance. (though I
find myself having to justify this to Oracle trained
DBA's) :)
What I
Yes, I agree it's unnecessary -- but you'll never have to worry about the
postmaster not starting due to lack of allocatable
memory -- when I was testing setups, I got sick of rebooting everytime I had to
make a change to /etc/system, that I threw up my
hands and said, "let it take all it wants".
... Trying again again with right email address -- list server rejected
previous :)
Hi, Paul
Josh helped my company with this issue -- PG doesn't use shared memory like
Oracle, it depends more on the OS buffers. Making shared mem
too large a fraction is disasterous and seriously impact performan
16 matches
Mail list logo
