Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pgaddict
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
26 ms
·
211.
▲
by
pgaddict
9y ago
And? Blaming everyone for "double speak" is rather counter-productive and a great way to destroy the discussion, as it ignores some people are actually interested in a honest discussion. What a wonderful way to create toxic enviro
212.
▲
by
pgaddict
9y ago
Not to mention that their website was pretty much constantly down during the recent period of Ethereum volatility. Whenever Ethereum price started to move (which is exactly the moment when people want to sell/buy) they would go tits up
213.
▲
by
pgaddict
9y ago
> All this talk about Oracle is just plain stupid. Oracle doesn't control anything, the community does. One core developer still works on Btrfs from Oracle, the vast majority of the contributions come from outside Oracle. FWIW I hav
214.
▲
by
pgaddict
9y ago
I partially disagree with the claim that ZFS is slower than ext4/xfs. It is, but only as long as you don't use ext4/xfs on top of LVM to get similar snapshot capabilities etc. Then ZFS starts to win. So if you only need a pla
215.
▲
by
pgaddict
9y ago
I think a natural follow-up question is "Why Red Hat does not have engineers to support btrfs?" That is, if the lack of engineers is a symptom, what is the cause? I'm pretty sure, had RH wanted they could either hire or assig
216.
▲
by
pgaddict
9y ago
Are you suggesting that's a problem with CoW in general, or with BTRFS implementation specifically? I would say ZFS works extremely well (at least for the workloads I care about, i.e. PostgreSQL databases, both OLTP and OLAP). I know a
217.
▲
by
pgaddict
9y ago
Yes, I've done some tests on BTRFS with nodatacow, and it improved the performance and behavior in general. Still slower tha XFS/EXT4, but better than ZFS (with "full" CoW). But as you mention, that does not say anything
218.
▲
by
pgaddict
9y ago
I find the suggestion that the technical issues are caused by the CoW design a bit strange. Sure, making the filesystem CoW-based means there are some inherent costs, but it allows the filesystem to implement some interesting features (e.g.
219.
▲
by
pgaddict
9y ago
Except that BKK is not a SME, but a company managing transportation in a city with nearly 2 million people. I've done work for similar organizations founded by municipalities (although smaller and not in Hungary), and pretty much all o
220.
▲
by
pgaddict
9y ago
That's unlikely. Every if you don't develop the system on your own and buy it from a third party (be it T-Systems or someone else), you still need technical expertise to prepare the requirements, evaluate the proposed solution (po
221.
▲
by
pgaddict
9y ago
I've actually used hangouts at the previous company (so roughly 2012-2015 or so), and it worked fine I guess. I don't remember what were the reasons not to use it instead of Skype, but I'm sure there were some. But I guess we
222.
▲
by
pgaddict
9y ago
That very much depends on what are your requirements. If you need all the stuff skype supported originally - chat, voice, video, screen sharing etc. then I don't have a solution I'm afraid, particularly if you need support for var
223.
▲
by
pgaddict
9y ago
I couldn't agree more. We've been using Skype for internal communication for a very long time. Back then it was the only option that worked on all the OSes we need (Linux, Windows, Mac), had all the features, and it just worked. B
224.
▲
by
pgaddict
9y ago
Thank God you haven't claimed it was webscale. We'd get nuts.
225.
▲
by
pgaddict
9y ago
Everything is "too new" at some point, and matures over time. But I don't know why a performance comparison would not be meaningful at this point? I mean, it may get obsolete soon, but it's the only way to guide optimiza
226.
▲
by
pgaddict
9y ago
I don't think Postgres was "NoSQL database as we understand the term today". The basis of NoSQL is not the lack of SQL but the non-relational data model. Postgres (mostly) sticks to the relational data model, although it perf
227.
▲
by
pgaddict
9y ago
So you want something that covers all types of database systems? I don't think any such book exists, but maybe look at the database-oriented courses at CMU, Berkeley, Stanford, MIT ... Those are typically comprehensive and include link
228.
▲
by
pgaddict
9y ago
Yes, at this point it's manual optimization task - you have to decide which statistics you need (e.g. by looking for poor estimates in query plans) and then create them. Pretty much just like indexes. The ultimate goal is to allow dete
229.
▲
by
pgaddict
9y ago
It's difficult to say whether the extended statistics could help with your schema, particularly in Pg10 where we only implemented two simple statistics types - functional dependencies and ndistinct (GROUP BY) coefficients. Maybe the ch
230.
▲
by
pgaddict
9y ago
I don't think PostgreSQL has issues with max_connections, it'll simply start rejecting new connection requests (as pointed out by davidgould). What we see in practice, though, is that people often increase max_connections to rathe
231.
▲
by
pgaddict
9y ago
I'm not particularly emotional about this, at least not in the "getting irrational" sense. And I'm not against intelligence agencies in principle, I acknowledge that we need them to some level. The difference is that I c
232.
▲
by
pgaddict
9y ago
A lot of the people on HN are not US citizens, and we don't give a fu*k about that distinction. All we see is an intelligence agency of our ally breaking into our companies/institutions, siphoning private data and wreaking havoc.
233.
▲
by
pgaddict
9y ago
Sadly this entirely skips the user registration, which probably includes the brain-dead variant of "security questions", essentially forcing you to choose from a fixed list of both questions and answers. Pretty much everyone told
234.
▲
by
pgaddict
10y ago
Yeah, although there's a difference between "publishing whatever" and "publishing books that copy from other books". Ultimately it's not the publisher but the author that matters, I guess.
235.
▲
by
pgaddict
10y ago
I just remembered there's also "PostgreSQL: Up and Running" published by O'Reilly. It deals with more stuff than just administration, but Regina O. Obe and Leo S. Hsu are good authors.
236.
▲
by
pgaddict
10y ago
I assume there will be some limitations what matviews can be updated automatically/ incrementally. E.g. updatable views (regular, not materialized) have a range of such restrictions, see: https://www.postgresql.org/docs
237.
▲
by
pgaddict
10y ago
That depends on what you mean by pluggable storage and how it's implemented ... For example PostgreSQL supported custom index access methods, which you might see as a custom storage format (although only for secondary storage). You had
238.
▲
by
pgaddict
10y ago
PL/SQL has various types of collections, for example, that are super-useful when you need to do more complicated processing without having to create temporary tables and such.
239.
▲
by
pgaddict
10y ago
There's still the aspect of handing over the control to a third party that may disappear next month, discontinue the features you rely on, etc. FWIW, I don't think the workflow is a major barrier. Do 'git format-patch' a
240.
▲
by
pgaddict
10y ago
Linux kernel is another such project, I think. One of the reasons why it's done this way (through mailing lists and not e.g. through pull requests on github) is that all the history is tracked in a way that's fully under control o
More ›