Pinning postgresql about conda-forge-pinning-feedstock HOT 3 OPEN

There has been some discussion of the bot issuing PRs for back updates.

from conda-forge-pinning-feedstock.

Relevant to interpreting the report, from here

PostgreSQL major releases include new features and occur roughly once every year. Beginning with version 10, a major release is indicated by increasing the first part of the version, e.g. 10 to 11. Before version 10, a major release was indicated by increasing either the first or second part of the version number, e.g. 9.5 to 9.6.

It seems historically like they've only ever broken backwards compatibility at major releases, and major releases are now defined in the normal 1-dot way, so CB3 default policy should be fine I think.

from conda-forge-pinning-feedstock.

If possible, I would like to continue building libraries/dependencies for both PostgreSQL 10.x and 9.6.x.

A lot of places still use the 9.6 series exclusively.

from conda-forge-pinning-feedstock.