RhodiumToad's profile picture. Find me on IRC: #postgresql or #freebsd on http://irc.libera.chat (he/him)

RhodiumToad

@RhodiumToad

Find me on IRC: #postgresql or #freebsd on http://irc.libera.chat (he/him)

Pinned

Verbosity and twitter are ... not suited to each other


Gotta love "no functional change" commits that actually cause 100% failure in an important use case


Every time I do anything that involves Linux I find new reasons to hate it.


SELECT 'Happy new year '||name FROM pg_timezone_names WHERE EXTRACT(year FROM now() AT TIME ZONE name) = 2021;


Pop quiz: posix_spawnp(&pid, "foo", ... envp) invokes a program "foo" using a search of the PATH env var. Should it use the value of PATH from the calling process' env, or the value from envp which will become the child's env? (spec at pubs.opengroup.org/onlinepubs/969… )

Caller's environ %66.7
Value from envp %33.3

12 vote · Final results


Today's fun fact: "Tory" comes from the Irish word for a bandit. Any relevance to modern politics is left as an exercise for the reader


PSA: When asking for help, show YOUR OWN code / problem description, don't just point to a random forum post and say "I'm having the same problem as this". It makes it impossible to see what simple errors you may have made, or differences between your issue and the post


Wow, @jimmy_wales blocked me, for pointing out the transparency problems with his social media site.


Another SQL style tip: always a space before the paren in constructs like "OVER (", "FILTER (", etc. Avoid making things look like function calls when they're not.


SQL style tip: treat "SELECT DISTINCT" as one keyword that happens to have a space in it. Never put a newline before DISTINCT, and never put an open paren directly after it. When using COUNT(DISTINCT ...), if you absolutely need a paren, then always have a space before it.


PSA: The error message is the part that starts with "ERROR:". Any DETAIL: or HINT: that follows may be informative, but it is NOT the error message. ALWAYS READ THE ERROR MESSAGE.


So now I'm curious: to the two people who voted to keep postfix operators in my poll: why? Do you have a use case or an example of existing usage?


Quick poll: should @PostgreSQL remove support for postfix operators in expressions, or keep them? Their existence makes parsing a lot harder.

Yes, remove them %93.5
No, keep them %6.5

31 vote · Final results


Today's #PostgreSQL optimization tip: when dealing with queries over many tables, consider increasing from_collapse_limit and join_collapse_limit. postgresql.org/docs/current/r…


I will probably regret signing up for this thing.


Loading...

Something went wrong.


Something went wrong.