I also have a question about warm standby replication.
What'd be the best solution for the system with 2 db servers (nodes), 1
database and 10 seconds max to switch between them (ready to switch time).
Currently I'm using Slony, but it's kind of slow when doing subscribe
after failover on the fa
On Fri, Aug 14, 2009 at 3:43 PM, Reid Thompson wrote:
> On Fri, 2009-08-14 at 14:00 -0400, Jeremy Carroll wrote:
>> I am confused about what the OS is reporting for memory usage on
>> CentOS 5.3 Linux. Looking at the resident memory size of the
>> processes. Looking at the resident size of all post
On 08/15/2009 11:39 AM, Jeremy Carroll wrote:
Linux strives to always use 100% of memory at any given time. Therefore the
system will always throw free memory into swap cache. The kernel will (and can)
take any memory away from the swap cache at any time for resident (physical)
memory for proc
Linux strives to always use 100% of memory at any given time. Therefore the
system will always throw free memory into swap cache. The kernel will (and can)
take any memory away from the swap cache at any time for resident (physical)
memory for processes.
That's why they have the column "-/+ buf
Jeremy Carroll writes:
> I am thoroughly confused that TOP is reporting that I have 99% of my
> physical RAM free, while the process list suggests that some are
> taking ~8Gb of Resident (Physical) Memory. Any explanation as to why
> TOP is reporting this? I have a PostgreSQL 8.3 server with 48Gb
If I have 10GB of ram, and I see a process using 5Gb of RES size. Then TOP
should at least report 5GB physical memory used (AKA: Not available in CACHED,
or FREE). If I run a 'free -m', I should only see 5GB of ram available. I can
understand with virtual memory that some of it may be on disk, t
