> On 16 Apr 2014, at 17:35, "Nick Eubank" wrote:
>
>
>
>
>> On Wed, Apr 16, 2014 at 1:29 AM, amulsul wrote:
>> >Anyone found a work around?
>>
>> Wouldn't it helpful, setting it in your session?
>>
>> set work_mem='2000MB';
>> set maintenance_work_mem='2000MB';
>>
>> do rest of sql after
> Hi all,
>
> A few years ago someone said postgres windows can't set working_mem
> above about 2 GB (
www.postgresql.org/message-id/17895.1315869...@sss.pgh.pa.us
> -- seems to be same for maintenance_working_mem ). Im finding
> limit still present.
Setting work_mem higher than 2GB on a 16GB m
Markella Skempri wrote on 26/03/2014
13:47:47:
>
> Thanks Martin,
> However this is a database dedicated server and nothing much else is
> running on it. Also, I never saw this happening with 9.2 – but I
> can’t vouch for the size of files that I was uploading.
>
>
> max is 1024mb.
> you have to test your workload if it's too low you will get too much
> i/o ( the filesystem cache could help.. not always /*nfs*/), if too
> high your cpu will be eated by lru/ latch/ and so on.
> Mat Dba
The max is most certainly NOT 1024MB.
http://www.postgresql.org/docs/9.
> I wanted to follow up from this question. I’m running on 9.3.4
> My DB server has 32GB ram so I have assigned 8GB
> shared_buffer_memory. It is quite a big db but with not much
> traffic. When there is traffic, it’s usually big.
>
> Lately, the kernel has been killing the postmaster for havin
> On Wed, Oct 17, 2012 at 1:53 AM, Martin French
> wrote:
>
> Thanks for your response.
>
> > What are the settings for:
> > work_mem
> 100MB
This is a little higher than I would ordinarily set. I tend to cap at
about 64MB
>
> > maintenance_work_mem
&g
>
> We've run into a perplexing issue with a customer database. He moved
> from a 9.1.5 to a 9.1.6 and upgraded from an EC2 m1.medium (3.75GB
> RAM, 1.3 GB shmmax), to an m2.xlarge (17GB RAM, 5.7 GB shmmax), and is
> now regularly getting constant errors regarding running out of shared
> memory (t
Hi Jim,> > I've already tried something very similar using dd. No performance> penalties during a normal running of the system - or when this blocking> happens either actually. But I agree, it does indeed sound like some> sort of I/O problem. I just don't know what! I do have a few more tricks> up
> > Hi> > > > > > > > We're seeing SELECT statements and even EXPLAIN (no ANAYLZE) > > > statements hang indefinitely until *something* (we don't know what)> > > releases some kind of resource or no longer becomes a massive bottle> > > neck. These are the symptoms.> > > > Is this in pgAdmin? Or psq
Hi> > We're seeing SELECT statements and even EXPLAIN (no ANAYLZE) > statements hang indefinitely until *something* (we don't know what)> releases some kind of resource or no longer becomes a massive bottle> neck. These are the symptoms.Is this in pgAdmin? Or psql on the console?> However, the syst
10 matches
Mail list logo
