Re: Postgres 8.x on Windows Server in production

You'll almost certainly want to use NTFS.

I suspect you'll want to set the NTFS Allocation Unit Size to 8192 or
some integer multiple of 8192, since I believe that is the pg page
size. XP format dialog will not allow you to set it above 4096, but
the command line format utility will. I do remember setting it as high
as 64k for SQL Server on Windows Server 2003 (SQL Server does IO in
8-page units called extents)
Someone please correct me if I have that wrong.

Do not allow any indexing service activity on the data or transaction
log volumes. If this is a dedicated database server you may as well
turn indexing service off.

Don't enable compression on the data or transaction log volumes either.

Pay attention to Automatic Updates - you likely don't want your
database server to restart every 4th Wednesday morning or so.

Hope this helps,
Justin
2009/4/13 Ognjen Blagojevic <ognjen(at)etf(dot)bg(dot)ac(dot)yu>:
> Hi all,
>
> First, thank you all for your answers.
>
>
> Grzegorz Jaśkiewicz wrote:
>>
>> Give it a try, and please tell us what sort of application you want to
>> put on it.
>
> It is a student database for the college which is a client of ours. The size
> of the database should be around 1GB, half being binary data (images). Not
> more than 100 users at the time will be working with the application.
>
> I don't worry about the performance, but more about the maintenance under
> Windows. What file system to use? How to schedule vacuuming and backup? Are
> there any windows services that should be turned off? Those questions come
> to my mind when I consider new OS for the RDBMS.
>
> Regards,
> Ognjen
>
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>