The following bug has been logged online:
Bug reference: 4575
Logged by: Scott Carey
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.5, 8.3.4
Operating system: Linux (CentOS 5.2 2.6.18-92.1.10.el5)
Description:All page cache in shared_buffers pinned (duplica
Hello,
I canot instal a postgre version 8.2.5...I have a 2 clicks on the doc. and
appears a box error:
This installation package can not be open Verify that the package exists
and that you can access it, or contact the application vendor to verify that
this is a valid Windows install package.
w
On Thu, Dec 11, 2008 at 5:37 AM, Scott Carey <[EMAIL PROTECTED]> wrote:
>
>
> Run top, and note the largest value of the "SHR" column on all postgres
> processes. Now execute the os cache eviction. Check the remaining cached
> memory.
> Note that it is now larger than the baseline by essentially
On Thu, Dec 11, 2008 at 2:05 PM, Pavan Deolasee
<[EMAIL PROTECTED]> wrote:
>
> Isn't the shared memory on Linux non-swappable, unlike Solaris where
> you have an option to make is swappable ?
Or may be my linux kernel knowledge is stale. I see a SHM_LOCK/UNLOCK
operations in shmctl(2) which can be
"Scott Carey" <[EMAIL PROTECTED]> writes:
> I have determined that nearly every cached page within shared_buffers is
> being pinned in memory, preventing the OS from dropping any such pages from
> its page cache.
Shouldn't you be complaining to kernel folk rather than here?
What do you think we co
Ok, I'll double check to validate that there is true duplication.
If shared memory cannot be swapped, and shows up in the page cache list (which
would be odd, but ok, since shared mem is not page cache it is application
memory), then only those pages (the actual shared_buffers) would not be
swa
I am 99.9% certian its not a fluke of "top" (or 'free'). Or a fluke with the
drop_caches linux vm signal. Otherwise, the system would not spin at 100%
System cpu getting no work done if an attempt to allocate memory above that
threshold, the original symptom that led me down this path of inves
Hi,
Yesterday I pull source from PG-Devel repository (Head) and was playing
around with ECPG. I got following two issues while parsing my script files
through ECPG preprocessor which I think are potential bugs;
1- I get this error message from preprocessor,
*ERROR: cursor "m_name_cursor" alread
Scott Carey writes:
> I am 99.9% certian its not a fluke of "top" (or 'free'). Or a fluke with the
> drop_caches linux vm signal. Otherwise, the system would not spin at 100%
> System cpu getting no work done if an attempt to allocate memory above that
> threshold, the original symptom that l
