Here are my few recommendations that might help you:
- You will need to do table partitioning (
http://www.postgresql.org/docs/current/static/ddl-partitioning.html) as you
are storing quite a lot of data in one table per day.
- You are using a RAID5 setup which is something that can also affect
Guy,
Did you tune postgresql ? How much memory does the box have? Have you
tuned postgresql ?
Dave
On 28-Dec-06, at 12:46 AM, Guy Rouillier wrote:
I don't want to violate any license agreement by discussing
performance, so I'll refer to a large, commercial PostgreSQL-
compatible DBMS
On Mon, 2006-12-18 at 16:18 -0500, Bill Moran wrote:
In response to Tom Lane [EMAIL PROTECTED]:
Bill Moran [EMAIL PROTECTED] writes:
Does the creation of a temp file trigger any logging?
No; but it wouldn't be hard to add some if you wanted. I'd do it at
deletion, not creation, so
Shoaib Mir [EMAIL PROTECTED] writes:
Here are my few recommendations that might help you:
[ snip good advice ]
Another thing to look at is whether you are doing inserts/updates as
individual transactions, and if so see if you can batch them to
reduce the per-transaction overhead.
Good day,
I have been reading about the configuration of postgresql, but I have a
server who does not give me the performance that should. The tables are
indexed and made vacuum regularly, i monitor with top, ps and
pg_stat_activity and when i checked was slow without a heavy load overage.
What are your table sizes? What are your queries like? (Mostly read,
mostly write?)
Can you post the analyze output for some of the slow queries?
The three things that stand out for me is your disk configuration (RAID
5 is not ideal for databases,
you really want RAID 1 or 1+0) and also that
Hi,
On 28-Dec-06, at 8:58 PM, fabrix peñuelas wrote:
Good day,
I have been reading about the configuration of postgresql, but I
have a server who does not give me the performance that should. The
tables are indexed and made vacuum regularly, i monitor with top,
ps and pg_stat_activity
