| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, amul sul <sul_amul(at)yahoo(dot)co(dot)in>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Server crash due to SIGBUS(Bus Error) when trying to access the memory created using dsm_create(). |
| Date: | 2017-09-24 22:11:39 |
| Message-ID: | CAEepm=3b+Wu81XgseDcc_a6JUC6_JCgyj41LGWfY1qto3gE1KA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 17, 2017 at 11:39 AM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> On Thu, Jun 29, 2017 at 12:24 PM, Thomas Munro
> <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
>> fallocate-v5.patch
>
> Added to commitfest so we don't lose track of this.
Rebased due to collision with recent configure.in adjustments. I also
wrote a commit message and retested with create-dsm-test.patch (from
upthread).
So, do we want this patch? It's annoying to expend cycles doing this,
but it only really hurts if you allocate a lot of DSM space that you
never actually use. If that ever becomes a serious problem, perhaps
that'll be a sign that we should be reusing the space between queries
anyway?
--
Thomas Munro
http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| fallocate-v6.patch | application/octet-stream | 5.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-09-24 23:06:49 | Re: [BUGS] BUG #14825: enum type: unsafe use? |
| Previous Message | Andrew Dunstan | 2017-09-24 21:32:29 | Re: BUG #14825: enum type: unsafe use? |