Thanks for the rapid response.
I can understand the way the planner makes its guess, but as a matter of
fact, he'll be nearly always wrong, just becausethe most commented articles
have only around 5000 or so comments. I ran the explain analyze tonight
and got this results :
EXPLAIN ANALYZE
Apologies if this is a FAQ, but...
Given linux's (mis)accounting/reporting of per-process memory, including
shared memory (see for example this page:
http://lwn.net/Articles/230975/) how does postgresql interpret and use
the information that's provided? Does it use the information as-is?
Does
On Wed, 21 Jan 2009, Dave Youatt wrote:
Does it just accept the configuration parameters provided (e.g. --
shared_buffers, effective_cache_size, etc.)?
That's it. The only time PostgreSQL gets a report from the OS related to
memory is if it makes an allocation attempt that fails. Couldn't
Greg Smith wrote:
On Wed, 21 Jan 2009, Dave Youatt wrote:
Does it just accept the configuration parameters provided (e.g. --
shared_buffers, effective_cache_size, etc.)?
That's it. The only time PostgreSQL gets a report from the OS related
to memory is if it makes an allocation attempt
Hi I am developing a database and have a couple of questions I havent
found an answer to yet.
1) how do I find the size of an index, i.e. the size on disk?
2) I have a query that is taking a long time to complete because the
table is about 120GB large. Its only returning 2000 rows, so in
Hi,
Thomas Finneid schrieb:
Hi I am developing a database and have a couple of questions I havent
found an answer to yet.
1) how do I find the size of an index, i.e. the size on disk?
i use this query:
select
t.spcname as tablespace
, pg_get_userbyid(c.relowner) as owner
,
