I even created an DB with one table and column and this still happened when queering it.
The problem here is the number of I/O writes. From 15 to 30... with lots of users this is becoming an issue.
Are you sure that moving to Linux will solve this? Could you please check if you notice the same write behavior? Any other windows users that noticed this?
Thank you in advance / Jennifer
On Wed, Jun 3, 2009 at 8:32 PM, Jennifer Trey <jennifer.trey@xxxxxxxxx> wrote:
Sorry.. the formatting got screwed.. here it is again :-----lol, if I had a nickel for every one that said they had a dollar I'd buy a Ferrari F430 :Pbut I do.. most of my memory isn't being used.. and I have once had a deep discussion on tuning postgres on this mailing list. Feel free to search on my name and you will see it :)But I have gotten even closer now to understanding this and changing the effective_cache thingy didn't help :(I have noticed that for every query that is ran on the DB the write happens, no matter if it is from my application or from some other place,15 I/O writes always occurs and has a size of approximatly 57kb each. The size differiates a little but it is always 15 writes! It doesn't matter if it is 2 queries (from the page) or 1 query or more. It seems to be on a connection basis. I opened up pgadmin and ran an sql query there and same thing happened. I don't understand how why the reads aren't increasing either, even if there is writes, there should be reads as well, right!?select * from ad where id >= 2 limi x ... where x could be anything and the nbr of writes was still constant and id is a primary key.It leaves me to believe that its either some logging like you mentioned Bill, but I have turned off it (at least I believe so) or that there is some PostgreSQL on Windows issues. I forgot to mention that I am running Postgre 32bit on Windows Server 2008 64bit. ??Also, the data that Postgre uses is on the same disk but on a different partition. Could it be that the writing is from one partion to another, but then there is the reading that should still occur. But perhaps its from the buffer or memory :O haha.. just guessing..It is possible that Windows permission system is forcing postgre to this behaviour. I have had numerous permission issues, where the OS after ( in postgreSql's case, was when I installed Tuning Wizard) took permission over files and therefore was no longer accisseble to Posgre (that hassle took me some time aswell)If you have a good suggestion or theories please let me know. Otherwise, I think I will move over to Ubuntu Server real soon! I can't stand this anymore! I always have to consider that its Windows screwing things up for me :) I think with linux I will at least be free of that :)Thank you / Jennifer
