Hello,
I am using PostgreSQL 8.3.7 and I am experiencing an issue similar to
the one I've already described some time ago:
http://archives.postgresql.org/pgsql-performance/2009-02/msg00261.php
Again, adding a LIMIT clause to a query, which is normally executing
very fast thanks to an index,
On Mon, Sep 28, 2009 at 4:43 AM, Kouber Saparev kou...@saparev.com wrote:
Hello,
I am using PostgreSQL 8.3.7 and I am experiencing an issue similar to the
one I've already described some time ago:
http://archives.postgresql.org/pgsql-performance/2009-02/msg00261.php
Again, adding a LIMIT
std pik wrote:
Hi all..
please, how can i tune postgres performance?
Thanks.
Thats a very generic question. Here are some generic answers:
You can tune the hardware underneath. Faster hardware = faster pg.
You can tune the memory usage, and other postgres.conf setting to match
your
On 9/26/09 8:19 AM, Greg Smith wrote:
This means that the question you want an answer to is if the OS cache
isn't really available, where does giving memory to shared_buffers
becomes less efficient than not caching things at all? My guess is
that this number is much larger than 10GB, but I
Didn't see the original message so I replied to this one.
On Mon, Sep 28, 2009 at 8:11 AM, Andy Colson a...@squeakycode.net wrote:
std pik wrote:
Hi all..
please, how can i tune postgres performance?
Start here:
http://www.westnet.com/~gsmith/content/postgresql/
--
Sent via