News for hackers. Stuff that matters.
Re:Nine ways to shoot yourself in the foot with PostgreSQL by jaggederest on Tuesday April 25, 2023 @04:09AM (#35697788)
There's the hoary old cliche about "if I was given three hours to cut down a tree with an axe, I would spend the first hour sharpening the axe" but in many cases it's really true. You can look like a superhero just by pointing out some small feature that makes life easier.

One time I pointed out that, rather than reordering the tables to make loading work with foreign key constraints, we could pause trigger execution, load all the data, and then resume the triggers. pg_dump can even do it for you if you pick the options right (might be default), in addition to natively ordering the data correctly, but if you're messing around with large SQL files anyway, it's helpful..

Re:Nine ways to shoot yourself in the foot with PostgreSQL by j45 on Tuesday April 25, 2023 @09:42AM (#35700343)
Clever architecture and approach that borders on a series or layers of simple decisions can often put perform clever coding and maintain a greater degree of flexibility.
Re:Nine ways to shoot yourself in the foot with PostgreSQL by j45 on Tuesday April 25, 2023 @02:43PM (#35704846)
iOS Typo

*put perform = outperform

Re:Nine ways to shoot yourself in the foot with PostgreSQL by couchand on Tuesday April 25, 2023 @10:27AM (#35700960)
Here to point out that Lincoln said "six hours to cut down a tree... four hours sharpening", and I think that ratio is better.

He wasn't the first to observe the general principle, it's at least as old as the Bible[0].

[0]: https://biblehub.com/ecclesiastes/10-10.htm