On 11/8/19 11:57 AM, Michael Lewis wrote:
> You certainly could choose to store as tstzrange, but why not use two
> fields?
>
> https://www.postgresql.org/docs/current/rangetypes.html
I would lean more to a composite type:
https://www.postgresql.org/docs/11/rowtypes.html
Range types are built around looking for values within the range,
whereas the OP is looking for two discrete values. The two field method
you suggest above also encapsulates that.
--
Adrian Klaver
adrian.klaver@aklaver.com
