PostgreSQL used by Lisk Core Built version can be updated to version 10 due to obtain the better performance and increase security.
Before that, all of the queries need to be tested if working.
Corresponding issue on lisk-build - https://github.com/LiskHQ/lisk-build/issues/295
Are we taking into account https://github.com/vitaly-t/pg-promise and https://github.com/vitaly-t/pg-monitor ? Please, @vitaly-t could you give us a hand regarding compatibility?
@4miners will we be accepting automatically any minor change and bug fixes from Postgres? i.e. 10.X.X. Please, @fchavant bear in mind for https://github.com/LiskHQ/lisk-docker/pull/98/files
I have been using PostgreSQL 10.x exclusively, since its inception in early 2017.
There are no known issues with it, safe to upgrade for you guys. And the performance gains are huge, on a good hardware, especially when using JSON queries, because this is where the modern PostgreSQL all going.
On another note, I have been battling with the underlying [node-postgres] driver to make them add support for multi-host configuration, even wrote my own generic [connection-string] for it, but no visible progress there.
@diego-G Yes, according to PostgreSQL's versioning policy - All users should upgrade to the most recent minor release as soon as possible.
Most helpful comment
I have been using PostgreSQL 10.x exclusively, since its inception in early 2017.
There are no known issues with it, safe to upgrade for you guys. And the performance gains are huge, on a good hardware, especially when using JSON queries, because this is where the modern PostgreSQL all going.
On another note, I have been battling with the underlying [node-postgres] driver to make them add support for multi-host configuration, even wrote my own generic [connection-string] for it, but no visible progress there.