| From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
|---|---|
| To: | Petar Djurkovic <petar(dot)djurkovic(at)cbs(dot)co(dot)rs>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: ram consumption |
| Date: | 2016-05-29 00:50:03 |
| Message-ID: | 7892676a-6a41-8f50-9eef-0d2d138e8d4a@archidevsys.co.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Please see message at the bottom of this post..
On 29/05/16 11:17, Petar Djurkovic wrote:
> Postgresql version is 9.4.4 also host have 128 GB RAM and 16 cores.
>
> Best Regards,
>
> Petar
>
> On 5/29/2016 12:16 AM, Gavin Flower wrote:
>
>> On 29/05/16 05:18, Petar Djurkovic wrote:
>>> I stop postgresql with "service postgresql stop" when I stop my web
>>> application, postgresql running on Ubuntu 15.
[...]
>> In this list, the convention is to post replies at the end (with some
>> rare exceptions),
>> or interspersed when appropriate, and to omit parts no longer relevant.
>>
>> The motivation of bottom posting like this: is that people get to see
>> the context
>> before the reply, AND emails don't end up getting longer & longer as
>> people reply
>> at the beginning forgetting to trim the now irrelevant stuff at the end.
[...]
Please stop posting at the beginning of your email reply!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2016-05-29 09:03:15 | Re: ram consumption |
| Previous Message | Petar Djurkovic | 2016-05-28 23:17:42 | Re: ram consumption |