-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert Treat wrote: | On Friday 05 November 2004 07:48, Gaetano Mendola wrote: | |>Neil Conway wrote: |> > Gaetano Mendola wrote: |> >> Right but we can create a new segment and use it too. I don't know how |> >> these segments are used but I used to do it in the past, of course you |> >> have |> >> to create a memory manager that handle not ccntinuous segments. |> > |> > The TelegraphCQ folks have already done this: |> > |> > http://archives.postgresql.org/pgsql-hackers/2003-05/msg00336.php |> > |> > I haven't had a chance to look at the patch, though. |> |>Not bad, however that post is more than one year old. Implement a resizable |>shared memory could really improve postgres performances ? |> | | | Well it certainly would in the sense that we could make the database a little | more self tuning.
Yes, but someone ( I do not remember who in this list ) is scared about to be "paged" during the night because the DB is slow because a planned changed autonomously. Unfortunatelly this is the "major" argument ( I do not understand why ) against have a database self tuning.
Regards Gaetano Mendola
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBi7qz7UpzwH2SGd4RAtaUAKC2Fij5hA9FF+TxFEGBq72LSGahpgCg4+D3 OTeNKU02YK8OgsJCaODZLn0= =CI+E -----END PGP SIGNATURE-----
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
