"Andy" <[EMAIL PROTECTED]> writes:
> I get the feeling the server is somehow missconfigured or it does not
> work at full parameter. If I look at memory allocation, it never goes
> over 250MB whatever I do with the database.

That is not wrong.  Postgres expects the kernel to be doing disk
caching, so the amount of memory that's effectively being used for
database work includes not only what is shown as belonging to the
PG processes, but some portion of the kernel disk buffers as well.
You don't really *want* the processes eating all of available RAM.

I concur with Chris K-L's comments that you should reduce rather
than increase your settings.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to