Embed Notice

@mischievoustomato @fwc @griffith @bigtony @sneeden

> i'm not sure. postgres is using 100% cpu, i assume it's reading shit, but at the same time my instance is in a non working state due to well, expired domain xDDD

it's unlikely postgres is banging all the cores at 100% due to an expired domain. start dumping out some postgres logs to see what's happening. this should not be happening unless you're on some single core vps and you've got some other process hitting it hard.