| From: | Stephen Cook <sclists(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Dawid Kuroczko <qnex42(at)gmail(dot)com>, Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Perceived weaknesses of postgres |
| Date: | 2008-02-15 00:15:10 |
| Message-ID: | 47B4D98E.5040801@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Magnus Hagander wrote:
> I would guess they're referring to the ability to "pin" a table into
> memory, so that it always stays in the cache regardless of what else the
> database is doing. There is a narrow use-case where this can be very
> useful, but it can also be a very dangerous tool (hint: if you pin a
> table that grows up to say 80-90% of your RAM size, your database will
> not be fast for anything else)
I know that MS removed this ability in SQL Server 2005 for pretty much
this reason; it's usefulness was greatly outweighed by people screwing
up their systems by not calculating things correctly.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | paul rivers | 2008-02-15 00:45:22 | Re: Perceived weaknesses of postgres |
| Previous Message | Phoenix Kiula | 2008-02-15 00:10:36 | Re: PG quitting sporadically!! |