On Thu, Aug 17, 2017 at 11:39 AM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> On Thu, Jun 29, 2017 at 12:24 PM, Thomas Munro
> <thomas.munro@enterprisedb.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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
