ncrease the time scale for id wrap around to long
past the likely life expectancy of the software we're building today.
--
Clifford Hammerschmidt, P.Eng.
Looking closer at the bit math, I screwed it up it should be 64 bits
time, 6 bit uuid version, 8 node, 8 seq, and the rest random ... which is
42 bits of random. I'll find the code in a bit.
--
Clifford Hammerschmidt, P.Eng.
On Tue, Nov 8, 2016 at 9:42 AM, Clifford Hammerschmidt <
tangl
).
Thanks,
-Cliff.
--
Clifford Hammerschmidt, P.Eng.
On Tue, Nov 8, 2016 at 6:27 AM, Jim Nasby <jim.na...@bluetreble.com> wrote:
> On 11/3/16 7:14 PM, Craig Ringer wrote:
>
>> 1) getting microseconds (or nanoseconds) from UTC epoch in a plugin
>>>
>>
>> Ge
lock for a user plugin to serialize access to its
shared state (I'm assuming that plugins must be reentrant)
3) creating a configuration variable for a plugin and accessing its values
in the plugin. (e.g. `set plugin.configuration_variable=1` or somesuch)
Thanks,
--
Clifford Hammerschmidt, P.Eng.
