mhov
mhov
ok did some C investigations here basically starting with this ``` Interval *span = PG_GETARG_INTERVAL_P(0); elog(INFO, "Interval { month: %d, day: %d, time: %ld }", span->month, span->day, span->time); ``` and...
k i've made the adjustments i described before. I no longer used this `const USECS_PER_DAY` in `time.rs`, but I liked the idea of it, i `allow(dead_code)`'d it. But i feel...
updated for #615
looks like testing failed trying to install pgx-cargo? Could this be a transient error?
@workingjubilee I made an attempt at the PgBox change, in it's `PgBox::::allocate()` form in the one place where a `pg_sys::Interval` would be created by us. There weren't many previous datum...
I had to add `pg_sys::{subtype}RANGEOID` shims for PG10 as bindgen can't get them in the form they're in `pg_type.h` looks like this ``` /* range types */ DATA(insert OID =...
Ok cool at which scope should I have this? on the range.rs and any range related tests? Or just the impl for the RangeSubtype trait?
excluded `Range` support from `pg10` with `#[cfg(not(feature = "pg10")]`
Will update asap. Thanks
Updated for #615