hello,
there is other performance problem on this request.
If you analyse query plan, you see that most of the time are lost during
sequencial scan, and you have 2 seq scan.
You have to create other indexes to match the request.
Postgresq is totally dependant on index to reach is performance
Hello every body,
I just discover a big not only big huge difference between NOW() and
CURRENT_DATE.
Did you already know about it and do you know why ?
DELETE FROM blacklist where bl_date < (NOW() - interval '2 DAY');
on 6 000 000 of records
699 ms
DELETE FROM blacklist where bl_date < (CUR
hello to all,
I've a question regarding the folowing comments.
How to estimate vacuum aggressiveness ?
It's for me very deficulte to setup the autovaccum setting correctly. It
seems for me that it is not enough aggressive, but when I change the
settings the autovacuum process is almost always
Hello,
I'm trying to install a solution to permit me to :
- Secure the datas, without RAID
- Giving ability to increase the potentiality of the database towards
the needs.
I have read about slony, DRBD, pgpool
I don't find the good system to do what I want.
I manage for now 50 millions o
if I use a second machine to replicate the database, I escape this
problem isn't it ?
If I understand right, could you tell me how to do desactivate fsync
please ?
Best regards
David
Merlin Moncure a écrit :
On Wed, Aug 6, 2008 at 6:12 PM, dforum <[EMAIL PROTECTED]> wrote:
H
Hello to all,
I have a Linux 2.6.24.2--std-ipv4-64 #3 SMP Tue Feb 12 12:27:47 CET
2008 x86_64 Intel(R) Xeon(R) CPU X5355 @ 2.66GHz GenuineIntel GNU/Linux
with 8Gb of memory. Using sata II disk in RAID 1 (I known that is bad,
but it would change has quickly I can).
I have a database of 38
