> Please note that PostgreSQL changed its versioning scheme with the release of version 10.0, so updating to version 10.2 from 10.0 or 10.1 is considered a minor update.<p>While this looks like an important update, note that it's not a new feature release.
From the release notes:
>Fix sample INSTR() functions used to help transition from Oracle(r) PL/SQL to PostgreSQL PL/pgSQL to correctly match Oracle functional behavior<p>TIL PL/pgSQL exists so I googled it. In the page for porting from Oracle PL/SQL:<p>>Instead of packages, use schemas to organize your functions into groups.<p>Does anyone know if there are plans to introduce packages in Postgres? Doesn't putting function in different schemas mean you have to grant select/update permissions to the schemas that talk to other schemas?<p>*edit:formatting
I'd like to see updated versions of PL/v8 ship. The situation with building v8 is so bad ( <a href="https://github.com/plv8/plv8/issues/251#issuecomment-364541059" rel="nofollow">https://github.com/plv8/plv8/issues/251#issuecomment-3645410...</a> ), that almost the entire cloud infrastructure (AWS, Heroku, Docker) is stuck with an ancient version of PL/v8.
It's a shame that Postgres 10 still ships with the abomination that is pgAdmin 4. You don't have a lot of other choices either (the pgAdmin 3 LTS version still throws error left and right when connection to a postgres 10 DB)