Re: Status of 8.3 patches

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Heikki Linnakangas wrote:
> Bruce Momjian wrote:
>> o Automatic adjustment of bgwriter_lru_maxpages
>>
>> We show this as waiting for performance results. I am thinking we
>> should hold this for 8.4.
>
> Agreed. I spent close to a week trying different benchmarks and
> configurations and simple test cases on a test server and my laptop, and
> couldn't demonstrate bgwriter making a positive impact in any
> configuration I tried. The theory behind the patch is sound, but it
> looks like a lot more testing and analysis is needed.

Wouldn't real world testing be needed to actually gain insight to this
patch?

Joshua D. Drake

>
>> o Error correction for n_dead_tuples
>>
>> This shows as waiting on another patch. Again, I am thinking to
>> keep it for 8.4.
>
> It was waiting on the "vacuum oldestxmin" patch, which didn't make it to
> 8.3. I don't care for the patch myself, but it was submitted well before
> feature freeze and deserves a review. It looks good to me at first glance.
>

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGyfZjATb/zqfZUUQRAltsAKClIbgh+r2ktW9MM8EO/rfp/TrsWACgq34w
RdjYafRztMrnxztwlpRhWzQ=
=Yfiq
-----END PGP SIGNATURE-----