JimNasby

4 ms·

1.
by JimNasby 6y ago
More than 4 GW of capacity has gone offline in the last few minutes, based on http://www.ercot.com/content/cdr/html/real_time_system_condi... . A significant chunk of load was shed as well. Frequency is swingi
2.
by JimNasby 6y ago
The grid has basically zero capability to change the voltage; frequency is all that matters. Frequency is so low that in the past hour any power line time base has fallen over 5.5 seconds behind. That’s a massive drop in frequency.
3.
by JimNasby 10y ago
Out of curiosity, is it inheritance you like, or just the partitioning aspect of it? I've actually used inheritance far more than partitioning, but I know of others that would love to see inheritance die.
4.
by JimNasby 10y ago
Something that might be very interesting would be combining https://www.torodb.com/ with Timescale. ToroDB is database agnostic (though they prefer Postgres). If you extracted the appropriate keys (including the timestamp)
5.
by JimNasby 10y ago
Not sure what you're trying to say about "requires no extensions"; Timescale is an extension that doesn't modify Postgres itself, similar to Citus, and very different from XL/XC, GreenPlum, or EnterpriseDB's pr
6.
by JimNasby 11y ago
FWIW, I got the impression that they didn't truncate the table, but just forced an update to it's relfrozenxid to advance the freeze age and allow the database to restart. That means there's a risk that rows that were current
7.
by JimNasby 11y ago
I think the real takeaway here is that any part of your underlying technology that you don't thoroughly understand puts you at risk, and that risk goes up significantly in a large volume environment. It's frequently not possible t
8.
by JimNasby 11y ago
You need to monitor how close you are to a wraparound. https://bucardo.org/check_postgres/check_postgres.pl.html#tx... is one way you could do that.