Sure.

I should note that we're moving to Linux for our production servers so
our interest in the Windows port is waning (at least for the time
being). In particular, the stuck WAL segment rename problem has
occasionally been rather a pain in the neck.

As long as we still have Windows test servers around though, it's easy
enough to apply a patch and load up the database to see if anything
interesting happens.

Pete

of
evidence to prove its usefulness. If you can try to apply it to your
*test*
server (8.0.*, 8.1.* are all ok), that would be very helpful to see
the
result.

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

With the patch applied, I let an inhouse stress test run for several
hours and it completed without incident. I also ran two runs of pgbench
with 50 connections x 1000 transactions and one run of 50 connections x
5000 transactions. All completed successfully. (Test server is a dual
Xeon with HyperThreading enabled, Windows Server 2003, PG 8.1.3).

Pete

of
evidence to prove its usefulness. If you can try to apply it to your
*test*
server (8.0.*, 8.1.* are all ok), that would be very helpful to see
the
result.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Great news. One question though - Win 2003 with or without SP1? Wasn't
this one of the things that showed up at least more often when you had
SP1 applied?

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Test server has SP1. This bug has only bit us twice (and never in a
testing environment) so it's hard to say (from our experience).

The successful pgbench runs are definitely good to see though.

Pete

this one of the things that showed up at least more often when you had
SP1 applied?


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq