Compiling 3a0e4d with -DCLOBBER_CACHE_ALWAYS causes initdb to segfault.
It looks like the tuple was allocated in the EventTriggerCacheContext,
and before the tuple was freed, another invalidation event came along
and wiped out that context.
It seems like the cleanest fix would be to explicitly al
meixiangm...@huawei.com writes:
> [ freshly-created sequence has wrong state after crash ]
I didn't believe this at first, but sure enough, it fails just as
described if you force a crash between the first and second nextval
calls for the sequence. This used to work ...
The change that broke it
