News for hackers. Stuff that matters.
Re:Let Postgres Do the Work (2013) by bbcbasic on Saturday November 26, 2016 @05:20PM (#13046243)
27s is still an awfully time. Why does it take so long?
Re:Let Postgres Do the Work (2013) by phereford on Saturday November 26, 2016 @05:25PM (#13046274)
We didn't make it immutable and we didn't add an index to it. Those are our next action items to help improve the performance of it.

Honestly, instead of looking into more performance gains, I wanted the team to get a huge win and for the team to look good in front of senior management :D.

Re:Let Postgres Do the Work (2013) by majewsky on Saturday November 26, 2016 @06:30PM (#13046658)
If you want to optimize for looking good in front of senior management, you would put a sleep() in there to make it run for 5 minutes. Then when senior mgmt comes back and complains that 5 minutes is still too much, you remove the sleep(), bill a few hours to time tracking, and praise the new performance improvements that you just deployed. ;)
Re:Let Postgres Do the Work (2013) by striking on Saturday November 26, 2016 @07:52PM (#13047019)
Re:Let Postgres Do the Work (2013) by majewsky on Saturday November 26, 2016 @08:55PM (#13047274)
Yes, this is exactly the article that I had in mind earlier. Thanks for digging it up.
Re:Let Postgres Do the Work (2013) by phereford on Saturday November 26, 2016 @07:08PM (#13046824)
Hahahahahaha.
Re:Let Postgres Do the Work (2013) by bbcbasic on Saturday November 26, 2016 @05:28PM (#13046293)
Ha ha politics driven development. Love it.
Re:Let Postgres Do the Work (2013) by phereford on Saturday November 26, 2016 @05:43PM (#13046379)
Ehh. More about boosting confidence and team morale than politics. The goal was achieved, and we can yak shave during slack time if need be.