Recent posts

For grades, that's fine. If it's money, don't use floats at all. Keep integer cents or use decimal.Decimal, and construct it from strings: Decimal("0.1"). Decimal(0.1) has the float's error in it alre…

No, it's how floats work. Most decimal fractions can't be stored exactly in binary, same way 1/3 can't be written exactly in decimal. Try 0.1 + 0.2 in Python. For display use round(x, 2) or a format s…

Adding up marks that have decimals and then the total is sometimes 79.99999999 instead of 80. Is my computer broken? The numbers are like 12.1 and 7.3.

Off. All good now, marking this one resolved.

You can leave it on and raise jit_above_cost, or turn it off for that role. For a small OLTP box I'd just turn it off.

880ms. Old package was built without LLVM support, turns out. Debian's has it.

There's your extra second. It has decided the query's expensive enough to compile. Was jit off in your old config, or was it a different package build? Try SET jit = off in the session and run it agai…

Top of it is: JIT: Functions: 42 Options: Inlining true, Optimization true, Expressions true, Deforming true Timing: Generation 8.1 ms, Inlining 310.2 ms, Optimization 612.4 ms, Emission 201.9 ms, Tot…

EXPLAIN (ANALYZE, BUFFERS) it and paste it. Change the table names if you need to.

Back to 20ms on most of it. Thanks. Still one report query that's slower than before, 2s where it was 900ms.

The in-stages version does a very rough pass first, so the worst of it clears up fast. Then finer passes. Check pg_stat_user_tables, last_analyze should be getting filled in.

Running. There's a line about it in the output I had scrolled past.

Oh.

Did you run the analyze step? pg_upgrade doesn't bring the planner statistics across, so right now it's guessing. It prints this at the end and everybody misses it. vacuumdb --all --analyze-in-stages

Upgraded a small Postgres box over the weekend with pg_upgrade --link. It came up fine, no errors. Queries that took 20ms now take 8 seconds. Same hardware, same config carried across. One example doe…

vek you have never had to explain a CGI to someone who just wants the bank site to load.

Write a one-button CGI that comments out the include. Thirty lines.

That's the correct reason. Pi-hole forwarding to local unbound is a common setup, nothing weird about it.

didn't know for-in order was random until a diff of two runs was different. pipe to sort every time

Already have the unbound blocklist from my other post. The argument for adding Pi-hole seems to be the web page, so my partner can turn it off without asking me. That might be worth it by itself.

this is the good kind of thread

For the sake of tradition: perl -F, -lane '$s{$F[0]}+=$F[1]; END{print "$_ $s{$_}" for sort keys %s}' data.csv

bump again. anyone?

I use this about twice a week and never see anyone else use it. awk -F, '{s[$1]+=$2} END {for (k in s) print k, s[k]}' data.csv Add | sort -k2 -n for ranked output. It breaks on quoted commas, so it's…

Yes, _physics_process runs at a fixed rate, and newer versions have physics interpolation you switch on in the project settings. Solved, thanks jf.