performance tuning - splitting data and logs

PostgreSQL is the database server used to store information. Do you have a question or are you having problem with PostgreSQL? If so, post them here.

Moderator: Moderators

Re: performance tuning - splitting data and logs

Postby kraada » Thu May 07, 2009 10:13 am

You're welcome and I'm glad we could get things sorted out for you :)
kraada
Moderator
 
Posts: 54435
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: performance tuning - splitting data and logs

Postby Traclugator » Sat Aug 22, 2009 11:02 am

Creating simlinks is quite scary for me :cry:
Would it be safer and easier to just paste the new path into .conf file instead of
#log_directory = 'pg_log'
in the section "ERROR REPORTING AND LOGGING" ?
Traclugator
 
Posts: 7
Joined: Fri May 16, 2008 12:48 am

Re: performance tuning - splitting data and logs

Postby kraada » Sat Aug 22, 2009 11:54 am

That should work as well.
kraada
Moderator
 
Posts: 54435
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: performance tuning - splitting data and logs

Postby Traclugator » Sat Aug 22, 2009 1:43 pm

kraada wrote:That should work as well.

What decision will be best for performance - tablespace on a fast (10k RPM) system HDD and logs on a spare disk (7200 RPM) or vise versa?
Traclugator
 
Posts: 7
Joined: Fri May 16, 2008 12:48 am

Re: performance tuning - splitting data and logs

Postby WhiteRider » Sat Aug 22, 2009 2:33 pm

Having your database on the fastest drive will give you the best performance. Writing logs to a separate disk will help because all the disk access on the DB drive will be concentrated on database access.
WhiteRider
Moderator
 
Posts: 53588
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: performance tuning - splitting data and logs

Postby Traclugator » Sat Aug 22, 2009 2:34 pm

WhiteRider wrote:Having your database on the fastest drive will give you the best performance. Writing logs to a separate disk will help because all the disk access on the DB drive will be concentrated on database access.

Ty ;)
Traclugator
 
Posts: 7
Joined: Fri May 16, 2008 12:48 am

Re: performance tuning - splitting data and logs

Postby Traclugator » Sat Aug 22, 2009 4:27 pm

OMG, looks that i was wrong.
The biggest disk usage is because of WRITE AHEAD LOG, but it seems to me that
#log_directory = 'pg_log'
is NOT for WRITE AHEAD LOG but only for error reporting :(
Write ahead dir. does not seem to be changed in conf file.
Traclugator
 
Posts: 7
Joined: Fri May 16, 2008 12:48 am

Re: performance tuning - splitting data and logs

Postby Traclugator » Sat Aug 22, 2009 5:13 pm

In my case i type
c:\Junction\junction c:\Program Files\PostgreSQL\8.3\data\pg_xlog "P:\PGSQL_WAL\XP"
but it always says

Error setting junction for c:\Program Files\PostgreSQL\8.3\data\pg_xlog:
????? ?? ?????.

I don't know what is ????? ?? ?????. looks like locale problem
Traclugator
 
Posts: 7
Joined: Fri May 16, 2008 12:48 am

Re: performance tuning - splitting data and logs

Postby WhiteRider » Sat Aug 22, 2009 5:25 pm

Traclugator wrote:...it seems to me that
#log_directory = 'pg_log'
is NOT for WRITE AHEAD LOG but only for error reporting


The # comments out the line. To change configuration you need to remove the #.
WhiteRider
Moderator
 
Posts: 53588
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: performance tuning - splitting data and logs

Postby Traclugator » Sun Aug 23, 2009 4:28 am

At last i've made all the junctions needed! But why my pg_xlog DIR is 850MB? :o Can i chanje it somehow? :?:
Traclugator
 
Posts: 7
Joined: Fri May 16, 2008 12:48 am

PreviousNext

Return to PostgreSQL [Read Only]

Who is online

Users browsing this forum: No registered users and 0 guests

cron