ref: 48bc71e185ca235f2192a2dbf6cb70dbd9de1aa1 jmp-schemas/deploy/plan_log_with_range.sql -rw-r--r-- 779 bytes

Creating with a literal stored the time that was 'now' when the view was
created. We want the current time when the view is accessed.
plan_log uses a tsrange instead of two timestamps now

This is honestly just more correct, but also allows for easy checking of
non-overlapping ranges, which we now do.