On Jan 18, 2008 2:14 PM, Greg Smith [EMAIL PROTECTED] wrote:
On Fri, 18 Jan 2008, Sean Davis wrote:
FYI, here are the specs on the server.
http://www.thinkmate.com/System/8U_Dual_Xeon_i2SS40-8U_Storage_Server
Now we're getting somewhere. I'll dump this on-list as it's a good
example
On Jan 17, 2008 6:23 PM, Greg Smith [EMAIL PROTECTED] wrote:
On Thu, 17 Jan 2008, Scott Marlowe wrote:
On Jan 17, 2008 2:17 PM, Sean Davis [EMAIL PROTECTED] wrote:
two3-ware cards, one 9640SE-24 and one 9640SE-16
Sounds like they're sharing something they shouldn't be. I'm not real
We have a machine that serves as a fileserver and a database server. Our
server hosts a raid array of 40 disk drives, attached to two3-ware cards,
one 9640SE-24 and one 9640SE-16. We have noticed that activity on one
controller blocks access on the second controller, not only for disk-IO but
also
On 10/15/05 9:20 AM, NSO [EMAIL PROTECTED] wrote:
Hello,
I am trying to select form table with bytea field. And queries runs very
slow.
My table:
CREATE TABLE files (file bytea, nr serial NOT NULL) WITH OIDS;
Query:
select * from files where nr 1450
(I have total 1500 records in
On 10/15/05 10:00 AM, NSO [EMAIL PROTECTED] wrote:
Hello,
How about some explain analyze output?
Explain analyse select * from files where nr 1450
Index Scan using pk on files (cost=0.00..3.67 rows=50 width=36)
(actual time=0.000..0.000 rows=50 loops=1)
I may not be understanding the
On 10/11/05 3:47 AM, Andy [EMAIL PROTECTED] wrote:
Hi to all,
I have the following problem: I have a client to which we send every night a
dump with a the database in which there are only their data's. It is a
stupid solution but I choose this solution because I couldn't find any better.
On 10/11/05 8:05 AM, Andy [EMAIL PROTECTED] wrote:
Do you have foreign key relationships that must be followed for cascade
delete? If so, make sure that you have indices on them.
Yes I have such things. Indexes are on these fields. To be onest this
delete is taking the longest time, but it
On Jan 26, 2005, at 5:36 AM, Leeuw van der, Tim wrote:
Hi,
What you could do is create a table containing all the fields from
your SELECT, plus a per-session unique ID. Then you can store the
query results in there, and use SELECT with OFFSET / LIMIT on that
table. The WHERE clause for this
