-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/17/07 17:12, mljv@planwerk6.de wrote:
> On Tuesday 17 July 2007 17:47:01 Tom Lane wrote:
>> mljv@planwerk6.de writes:
>>> i think i got it fixed as i saw that i pushed my maintenance_work_mem too
>>> high. It was higher than physical ram :-(
>> Ooops, that will definitely cause problems.
>
> yes it did! I ran it again. And now it takes 10 minutes per index instead of
> 10 hours (still 8.1). maybe something postgres should complain about if
> setting maintance_work_mem too high.
Unless it does some really OS-specific calls, *can* PostgreSQL know
how much *physical* RAM is in a box?
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGnk+zS9HxQb37XmcRAsDtAKCCadB0CF8ATeHCtO79wcTD3lER7wCgttoF
E9Rndryd/IhZEP2FY7yIr/A=
=bDSf
-----END PGP SIGNATURE-----
