Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: (Fwd) Re: [PATCH] db/gdbm rewrite
- X-seq: zsh-workers 40582
- From: Sebastian Gniazdowski <psprint2@xxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: (Fwd) Re: [PATCH] db/gdbm rewrite
- Date: Sun, 19 Feb 2017 01:01:20 -0800
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=JSQBfLuOFZEcFyP/ZC00QXG1hm c=; b=hD/4TAkEzgFj2SY4WUSWyAFYxX8QwWCahyONA2ihhHstLMiFNrR+T5Et5L oRRsO41y95++b7T/zSRbaxwPc98Jat7fqM/YjEhDgnpjDIC4X+EgsL/xBby+Lh9u zeGzkwYny2FGYG/ZJkRECD5kIhybutaHS3BIWZMpzpAe8Gwsc=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=JS QBfLuOFZEcFyP/ZC00QXG1hmc=; b=XB4iE3iP8zsy5NcjTEwaCCji0OQ3bOY/ix axtv65eQIj9ybAKdce1+Vi8Yh6RUAlLtKDUFFcu45xKc4Y6+ZPJ7zx0YcvIVKg02 coK7TRY3dSRfB+515D+rAhQLa4pQ3m0OPruB+qFUCrQm6i+al3T6v5+ChLb2F4iV /4e7fWDSE=
- In-reply-to: <1487494013.288657.885684608.5BB76024@webmail.messagingengine.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <170218164313.ZM10688@torch.brasslantern.com> <1487494013.288657.885684608.5BB76024@webmail.messagingengine.com>
On Sun, Feb 19, 2017, at 12:46 AM, Sebastian Gniazdowski wrote:
> change in Zsh forked process is a hole. It can be turned into an
> feature, though. A new builtin "zgdbmfetch paramname key" could be
> provided to re-fetch element when someone is going to try to do
> concurrent access with inherited FD and GDBM_SYNC lock, say with use of
> zsystem flock on other FD.
PS. Doing "fetch" might seem not nice in "hash-as-database" frontend,
but it would just clear PM_UPTODATE flag, rest is automatic. So maybe
"zgdbmclear param key". In my gdbm update I allocate regular Params
instead of heap-arena-ghosts, access database only when needed
leveraging PM_UPTODATE and GDBM_SYNC, it might be even possible to open
database without GDBM_SYNC and do locking with a "gdbmlock" builtin.
--
Sebastian Gniazdowski
psprint2@xxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author