Page 3 of 5

Re: performance tuning - splitting data and logs

PostPosted: Thu May 07, 2009 10:13 am
by kraada
You're welcome and I'm glad we could get things sorted out for you :)

Re: performance tuning - splitting data and logs

PostPosted: Sat Aug 22, 2009 11:02 am
by Traclugator
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" ?

Re: performance tuning - splitting data and logs

PostPosted: Sat Aug 22, 2009 11:54 am
by kraada
That should work as well.

Re: performance tuning - splitting data and logs

PostPosted: Sat Aug 22, 2009 1:43 pm
by Traclugator
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?

Re: performance tuning - splitting data and logs

PostPosted: Sat Aug 22, 2009 2:33 pm
by WhiteRider
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.

Re: performance tuning - splitting data and logs

PostPosted: Sat Aug 22, 2009 2:34 pm
by Traclugator
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 ;)

Re: performance tuning - splitting data and logs

PostPosted: Sat Aug 22, 2009 4:27 pm
by Traclugator
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.

Re: performance tuning - splitting data and logs

PostPosted: Sat Aug 22, 2009 5:13 pm
by Traclugator
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

Re: performance tuning - splitting data and logs

PostPosted: Sat Aug 22, 2009 5:25 pm
by WhiteRider
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 #.

Re: performance tuning - splitting data and logs

PostPosted: Sun Aug 23, 2009 4:28 am
by Traclugator
At last i've made all the junctions needed! But why my pg_xlog DIR is 850MB? :o Can i chanje it somehow? :?:

highfalutin