We're having an issue with our warm standby server. About 9:30 last night, it
stopped applying changes it received in WAL files that are shipped over to it
as they are created. It is still reading WAL files as they delivered, as the
startup_log.txt shows, but the changes in the primary database
I'm hoping someone can help me figure out how to better tune my WAL parameters.
Right now I am seeing WAL activity that is faster than I think it should be -
we average about 30 write queries a second at our peak, and yet we're getting a
new WAL file every 15-20 seconds.
Our postgresql.conf p
phpPgAdmin works great for me! You can do most simple queries without any SQL,
including add, select, update, sort (order by), alter, create, drop, etc etc.
All that can be done just by clicking buttons and labels in the browser. There
is the ability to execute actual SQL queries if your users k