[GENERAL] out of memory errors

Hi All, I need some assistance with a particular out of memory issue I am currently experiencing, your thoughts would be greatly appreciated. Configuration: [1] 3 x ESX VM's [a] 8 vCPU's each [b] 16GB memory each [2] CentOS 6.5 64-bit on each

Re: [GENERAL] out of memory errors

Hi, On 2014-06-16 13:56:23 +0100, Bruce McAlister wrote: > [1] 3 x ESX VM's > [a] 8 vCPU's each > [b] 16GB memory each > # Dont hand out more memory than neccesary > vm.overcommit_memory = 2 So you haven't tune overcommit_ratio at all? Can you show /proc/memin

Re: [GENERAL] out of memory errors

Hi, On 16/06/2014 14:15, Andres Freund wrote: Hi, On 2014-06-16 13:56:23 +0100, Bruce McAlister wrote: [1] 3 x ESX VM's [a] 8 vCPU's each [b] 16GB memory each # Dont hand out more memory than neccesary vm.overcommit_memory = 2 So you haven't tune overcom

[GENERAL] eclipse-gdb

hi, How do we debug specific functions in gdb of eclipse. Whenever I give break points in nodenestloop.c, it goes to main.c and finally the process ends there, The control never comes back to nodenestloop, how can we the proces constrained only to nodenestloop. Thank you

Re: [GENERAL] eclipse-gdb

Ravi Kiran writes: > Whenever I give break points in nodenestloop.c, it goes to main.c and > finally the process ends there, The control never comes back to > nodenestloop, how can we the proces constrained only to nodenestloop. If gdb sort-of-works but seems to get confused about specific breakp

Re: [GENERAL] out of memory errors

I was reading in to the parameter a little more and it appears that the defuault for vm.overcommit_ratio is 50%, I am considering bumping this up to 95% so the sums look like this: max memory allocation for process = swap + ratio of physical memory 21 + (16 * 0.95) = 36.2GB This in theory sho

[GENERAL] (Relatively) Oversized Checkpoint

We're still learning to tune PostgreSQL for our production setup, and over the weekend we saw a huge spike in INSERT/UPDATE completion time for a short period which turned out to correlate to an oversized checkpoint. I've included the preceding and following checkpoints for reference points, as the

Re: [GENERAL] (Relatively) Oversized Checkpoint

On Mon, Jun 16, 2014 at 11:01 AM, Nathaniel Talbott wrote: > We're still learning to tune PostgreSQL for our production setup, and over > the weekend we saw a huge spike in INSERT/UPDATE completion time for a short > period which turned out to correlate to an oversized checkpoint. I've > included

[GENERAL] Creating Table Copy

I have a table with some NULL values in a date column. I need to make a copy of that table containing only those rows where the date column is not null. Reading the CREATE TABLE man page I've tried to create a copy of the original table from which I could drop rows. While the table creating is s

Re: [GENERAL] Creating Table Copy [RESOLVED]

On Mon, 16 Jun 2014, Rich Shepard wrote: While I suspect there's a way to write a SELECT statement for those rows that are not null and save the results to a different table name, I've not found the syntax in my postgres and SQL references. Got it: # create table benthos as select * from

[GENERAL]

unsubscribe

[GENERAL] How to store fixed size images?

We have many small size(most fixed size) images, how to store them? There are two options: 1. Store images in folders, managed by os file system, only store path in postgresql 2. Store image as bytea in postgresql How do you usually store images? Thanks! peng

Re: [GENERAL] Creating Table Copy

On Tue, Jun 17, 2014 at 5:51 AM, Rich Shepard wrote: > I have a table with some NULL values in a date column. I need to make a > copy of that table containing only those rows where the date column is not > null. Reading the CREATE TABLE man page I've tried to create a copy of the > original tabl