Eric Davies

Probably in legacy or migrated systems. There are also databases that can communicate with libpq that aren't PostgreSQL, like Redshift.

https://github.com/postgres/postgres/blob/e94c1a55dada49772622d2be2d17a2a9973b2661/src/backend/utils/adt/timestamp.c#L980 The `AdjustIntervalForTypmod` function looks difficult to understand. Mostly I think it is truncating, but I'm not sure what the [precision](https://github.com/postgres/postgres/blob/e94c1a55dada49772622d2be2d17a2a9973b2661/src/backend/utils/adt/timestamp.c#L1467) section does and I don't have time to look...

Okay this is pretty great! And best of all it's optional so if someone's using a database which uses the PostgreSQL wire protocol but not the parameter syntax (i.e., `$1,...

> Yes I tried this, but I found it has a big downside: interpolations aren't syntax-highlighted. In practice I felt this quite outweighed the benefits of a string macro for...

Fix is to set `linkcheck_timeout` to something large enough to avoid these timeouts (it's a keyword argument to makedocs)

Maybe we should just switch to Coveralls if Codecov is giving us so much trouble

> After all, if a link needs retrying to succeed, it makes sense for the link-checking to fail. This makes sense to an extent; it's reasonable to include any retrying...

We'll have to be more careful than that. There would be conflicts. But we should just clear up those conflicts I think.

Conflicts between Iterators and IterTools were cleared up. We can do this, but we won't be able to export everything (e.g., we can't export `filter` as it's different than `Base.filter`).

You would probably want to use https://github.com/JuliaGeo/LibGEOS.jl I would recommend using the PostgreSQL function `ST_AsEWKT` in your query and then parsing with `readgeom` from LibGEOS.jl. Or you could use `ST_SetSRID(ST_MakePoint(lon,...