| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Missing checks when malloc returns NULL... |
| Date: | 2016-09-01 13:30:10 |
| Message-ID: | CAB7nPqTiR24Tcf8fLiPzrxCrELLEy5Uo_tVThJK3c8ThMhUDvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 1, 2016 at 10:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
>> Also, we could take one extra step forward then, and just introduce
>> ShmemAllocExtended that holds two flags as per the attached:
>> - SHMEM_ALLOC_ZERO that zeros all the fields
>> - SHMEM_ALLOC_NO_OOM that does not fail
>
> Don't see the point really ... it's just more API churn without any
> very compelling reason.
OK, then no objection to your approach. At least I tried.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-09-01 13:39:39 | Re: Choosing parallel_degree |
| Previous Message | Tom Lane | 2016-09-01 13:24:48 | Re: GIN logging GIN_SEGMENT_UNMODIFIED actions? |