HN user
Your backend needs to store location because places can switch time zones.
For the event, your backend only needs to store the timestamp in a timestamptz field and make sure that clients set the correct time zone on session start (this you might want the backend to store in the database too, but probably in the users table).
The last time I checked, audio and video firmware wasn't there.
I'm surprised that not only is there no application firewall for any of the BSDs, there doesn't even seem to be any need for it. There is OpenSnitch, but only for Linux.
I'd be interested in learning which commands you have in mind and what specifically is a bit nicer about their coreutils implementation.
Unless you're Tom, you'll have to work on tickets assigned to you by some manager.
In a world where HA is key, PostgreSQL has nothing to offer.
Give Mastodon a threaded view and technically it's the same as reddit, but federated? Usenet, but not just for nerds.
While waiting for PG 16 you can upgrade to 15.
So you DO search for answers to mainframe questions on s**overflow?
Postgres actually does have thousands of engineers but it's not easy to notice because they all share the same name.
https://www.citusdata.com/blog/2017/04/20/analyzing-postgres...
Not for free (have to pay EnterpriseDB for that). Every free option here is basically "glue pieces together to build your own HA".
Gavin's personal project is being used in production.
The BSD answer to the problems with strncpy() was to introduce a new function called strlcpy()
Not BSD, it was OpenBSD specifically.
Have you tried auditing ZFS? That's way too much code to be secure, it's best for OpenBSD to never import it.
Don't know what keeps him going. A desire to see FreeBSD fix those defaults?
And when they do fix any of those things, what is his reaction going to be? So far it's been "it took them so much time to fix this, let's keep that in mind".
The point of it is clearly to convince people to use OpenBSD instead of FreeBSD.
The flag is called in-place for a reason.
What's the reason? Surprisingly, the file is never edited in place.
How is backup restoration any easier if your whole PostgreSQL cluster goes back in time when you only wanted to rewind that one tenant?
Cassandra may be great when you have to scale your database that you no longer develop significantly. The problem with this DB system is that you have to know all the queries before you can define the schema.
You can disable building the "whole fucking C compiler suite" using WITHOUT_CLANG as documented in https://www.freebsd.org/cgi/man.cgi?query=src.conf
By the way, as an example, you can also disable IPv4 and IPv6 in the kernel, I'm not sure how to do it in Linux.
They mean: lose one drive and have another with bit rot.
- "RAID is not a backup" primarily because "you could rm -rf". ZFS snapshots cover that failure mode to the same extent that synchronization with offsite does, but cheaper. ZFS snapshots obviously don't cover other failure modes like natural disasters or a break in, so RAID is still not a backup.
- for ZIL to do its work properly, you need the disks not to lie when they claim that the data has been truly saved. This can be tricky to check, so perhaps think about a UPS
- if you have two M.2 slots you could use them to mirror two partitions from two different disks for your data pool's SLOG. The same could be done to form a new mirrored ZFS pool for the OS. In my case I even prefer the performance that a single-copy SLOG gives me at the risk of losing the most recent data before it's moved from the SLOG to the pool.
we really integrated S3 into the storage
Will it be possible to use something else in place of S3? I'm thinking on-premise or what some would call a private cloud.
They have a history of working with open source projects only to the extent that allows them to push some of their work upstream so that the burden of maintaining it is shared, while retaining the rest of it as proprietary solutions that give them advantage over competing businesses.
- "most recent" is usually best done with a max() with an adequate index or, when that's not possible, with a LATERAL JOIN, an ORDER BY and a LIMIT 1
- SELECT id FROM users WHERE EXISTS (SELECT 1 FROM story_comment WHERE story_id = 4 AND story_comment.user_id = users.id)
SELECT DISTINCT is rarely the best idea. In most cases it means someone is using joins to filter out rows that should have been removed with EXISTS (a semi-join).
It uses OpenZFS.
This is easy to say when you don't have to comply to some industry standards.
There's so much churn on hacker news that everything gets old after a couple of nanoseconds. So I think it would be best to just add a field for a 128-bit timestamp of the original submission and present it with high precision.
The Raspberry Pis are hostile towards non-Linux systems.