| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Gunther <raj(at)gusw(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)lists(dot)postgresql(dot)org, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Subject: | Re: Out of Memory errors are frustrating as heck! |
| Date: | 2019-04-15 13:44:40 |
| Message-ID: | CAMkU=1zpZk5Yq8dn=Hs6+ZapMH-ph65osYjrrdxsor2o2unC9Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sun, Apr 14, 2019 at 11:59 PM Gunther <raj(at)gusw(dot)net> wrote:
> Is there any doubt that this might be a problem with Linux? Because if
> you want, I can whip out a FreeBSD machine, compile pgsql, and attach
> the same disk, and try it there. I am longing to have a reason to move
> back to FreeBSD anyway. But I have tons of stuff to do, so if you do not
> have reason to suspect Linux to do wrong here, I prefer skipping that
> futile attempt
>
I think the PostgreSQL leaking in the first place would be independent of
Linux being ungraceful about it. So repeating it on BSD probably wouldn't
help us here. If you want to take up the 2nd issue with the kernel folks,
having some evidence from BSD might (but not very likely) be helpful for
that, but that would be for a different mailing list.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mahmoud Moharam | 2019-04-15 15:02:20 | iscsi performance |
| Previous Message | Jeff Janes | 2019-04-15 13:32:09 | Re: Out of Memory errors are frustrating as heck! |