Greg Smith wrote:
In practice, the ordered
mode (the default for ext3) seems sufficient to prevent database
corruption. There is a substantial performance hit to running in full
journal mode like you're doing;
where do you see which mode I am running in? I havent specified any
modes in
On Fri, 5 Sep 2008, Duan Ligong wrote:
Well, we could not wait so long and just moved the old clog files.
Congratulations. You have probably just destroyed your database.
Matthew
--
Lord grant me patience, and I want it NOW!
--
Sent via pgsql-performance mailing list
Considering a quad core server processor, 4 GBs of RAM memory, disk Sata
2.
What is the recommended setting for the parameters:
max_connections:70
max_prepared_transactions?
shared_buffers?
wal_buffers?
max_fsm_relations?
max_fsm_pages?
Atenciosamente,
Jonas Rodrigo
--
Sent via
Considering a quad core server processor, 4 GBs of RAM memory, disk Sata
2.
What is the recommended setting for the parameters:
max_connections:70
Depends on how many clients that access the database.
shared_buffers?
I have mine at 512 MB but I will lower it and see how it affects
I seem to have answered my own question. I'm sending the answer to the list
in case someone else has the same question one day.
According to the NetApp documentation, it does protect me from partial page
writes. Thus, full_page_writes = off.
On Wed, Sep 3, 2008 at 12:03 PM, Nikolas Everett
You might get great improvement for '%' cases using index on
channel_name(field,
start_time) and a little bit of pl/pgsql
Basically, you need to implement the following algorithm:
1) curr_field = ( select min(field) from ad_log )
2) record_exists = ( select 1 from ad_log where field=cur_field
Duan Ligong wrote:
Greg wrote:
On Tue, 2 Sep 2008, Duan Ligong wrote:
- Does Vacuum delete the old clog files?
Yes, if those transactions are all done. One possibility here is that
you've got some really long-running transaction floating around that is
keeping normal clog
On Thu, Sep 4, 2008 at 8:58 PM, Duan Ligong [EMAIL PROTECTED] wrote:
Thanks for your reply.
Greg wrote:
On Tue, 2 Sep 2008, Duan Ligong wrote:
- Does Vacuum delete the old clog files?
Yes, if those transactions are all done. One possibility here is that
you've got some really
On Fri, 5 Sep 2008, Jonas Pacheco wrote:
max_prepared_transactions?
This is covered pretty well by the documentation:
http://www.postgresql.org/docs/current/static/runtime-config-resource.html
There are suggestions for everything else you asked about (and a few more
things you should also
