Recently we migrated our first client to postgres 10.1, the database used to run on 9.2.
Everything went smooth with a total downtime of 12 seconds but obviously monitoring broke so i had to fix that and i thought to share the new statements to save people some trouble.
The statements that broke had to do with the change of xlog -> wal (and location -> lsn) which mostly affected replication monitoring statements. Bellow is what i used to have on PG 9 and what i got for PG 10.
Replication Slot monitoring Postgres 9:
Replication Slot monitoring Postgres 10:
Replication Lag monitoring Postgres 9 :
Replication Lag monitoring Postgres 10 :
Thanks for reading.
OmniTI Computer Consulting
Today i will try to show how strong Postgres 10 is by combining different features in order to create a "distributed" reporting se...
Lately, i wanted to make a new test / lab environment that would be dispensable, fast to deploy and easily customisable. VM's are all...
Yesterday, i came across a conversation in postgres slack channel, someone was interested in upgrading his database and i realised that the...
Postgres provides a lot of information when it comes to statistics. Only problem is that all the statistics are frozen in time the moment y...