adeel_siddiqui

Hibernate has actual prepared statements and binds values when the query is executed.

set `enable_seqscan` = 'off' or set local `enable_seqscan` = 'off'. This will force the pg query planner to use indexes. Experiment with it until you figure out why your query performance deteriorates. Maybe you are doing a lot of updates/deletes? Increase the statistics sampling size? Autovacuum more frequently?

Nice write-up. Something does not add up here though. Primary writes 32 ahead to the WAL when fetched the first time, then keeps a counter (log_cnt) which it decreases each time nextval is called. So, when sequence was initialized, nextval is 1 and WAL has 32. The replica sees 32 as fetched offset. How does incident sequence switch from 7 to 39? Shouldn't it be 33 when the replica was made the primary? Same for incident 20 -> 52, shouldn't it be 33 when replica was made primary? Unless I am missing something here, i.e, 32 is added to the nextval and nextval is logged each time (20 or 7).

Honestly, when the URL bar on Firefox started to get fatter on focus with the latest update, i found it a bit distracting. It was a sudden change to a component which people use the most and the behavior had been quite stable for some time. So, i guess that could have put off a few people and we started complaining ¯\_(ツ)_/¯

Frontend development/UI/UX design has gotten stuck in a weird loop. Many companies/startups get working on redesigning the UI every 6 months just because some competitor has a new design and a few people like it, or even worse, the designer likes the new "slick" design. It is bad because it is no longer concerns/standards about accessibility or usability driving those constant redesigns but some kind of self-created pressure to be part of a rat race.

Well, SAP has for long been a money making blackbox for consulting firms. Think IBM, Accenture and the likes. They rake boatloads of money for multi-year contracts to implement SAP systems for companies wanting ERP solutions. The system is outdated and obscure with both technical and non-technical people having a tough time understanding it. Last time I worked with some interfacing systems to some SAP modules, it still relied on web services, XML and SOAP. No REST support. Salesforce is on the same road. In a few years, they will spin up more modules apart from CRM, like manufacturing and payroll.

Good point. If you are doing this, you also need a good autovacuuming strategy on your pg database. Depending on the size of the tables and the frequency of DELETEs, not vacuuming regularly could potentially cause problems like bloated size on disk, slow queries, etc.