3

Performance is not relevant, use one user per website for both traceability and security, that way if you ever get any performance issues you can more easily track which site it relates to.


2

(Approximately in order, least-invasive to most-invasive. Backup the Replica -- IF you already have such. Not fast, but has no impact on the Primary. LVM Snapshot -- This almost instantly makes a "copy" of the entire disk. This, also, requires setup. Other forms of disk copy. (But you need to be careful about what gets copied.) Percona has a ...


1

If you set up Postgres replication by sending write-ahead log as described in streaming replication manual, then yes, all replicas are in the permanent recovery state which is normal. As write transactions are performed against the master node, the replicas receive and apply logs from the master, as any Postgres server in recovery would do. The changing ...


1

The absolute best way is to create a replica and then backup the replica. This way won't lock your DB tables when mysqldump cycles through the tables of your DB. There are many, many tutorials online that can help guide you through the process of setting up a read-only replica of your DB. If you use something like Commvault or NetBackup, they have commercial ...


1

Seems like ~45 connections / 2gb of Ram I saw formulas, checked my config and it has way more complicated formula for max_connections by default and was having hard time to count what is real limit, so did in simple way - just tested. Monitoring dashboard shows red line when reaching close to the limit. Check below. db.t3.small (2gb ram) Chart from ...


Only top voted, non community-wiki answers of a minimum length are eligible