Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fdr
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
33 ms
·
271.
▲
by
fdr
14y ago
In this form, Canonical overstates an appropriate objective in the tips: support more hardware? How about supporting any , thoroughly? I have done my best to buy hardware that I thought was to be well supported (on the desktop! because I t
272.
▲
by
fdr
14y ago
> Yes, fair enough. In such a case, why not use an explicit index like letters of the alphabet, in other words why not reindex the table just once, hierarchically, with something relevant to table searches, in a way that breaks the tabl
273.
▲
by
fdr
14y ago
Sometimes you really do have 100 million like-things. Partitioning can also be thought of a very compressed form of index, most of which are implement as some hierarchical data structure. This kind of hack basically is because of a weakne
274.
▲
by
fdr
14y ago
In the class of programmer given as an example, I think a lot of the answer is some amount of self promotion. This is not meant in a derogatory way: it is true some people self promote to the exclusion of doing something actually interesti
275.
▲
by
fdr
14y ago
One-dimensional arrays can be useful for indexing. See: GIN, and here's an example: http://stackoverflow.com/a/4946888 This uses the same underlying indexing method often used with Full Text Search. Values in arrays can be awkward if you
276.
▲
by
fdr
14y ago
SQLite does not have very many execution methods or a very intelligent optimizer, and every database has different access methods available to it to some extent. For example, Postgres lacks skip scan, which Oracle has. MySQL lacks bitmap
277.
▲
by
fdr
14y ago
> Needing lots of expensive invariants is almost "invariably" (see what I did there?) a code smell. What's your definition of need? I want a lot of invariants if because I have found it reduces the chance of error. This is also the f
278.
▲
by
fdr
14y ago
> So far we've established that: 1. you run with assertions always on in production, 2. you have encountered errors caught by the always-on assertions in production No. I gave two examples, one where assertions are run in production (mo
279.
▲
by
fdr
14y ago
> It seems like your experiences confirm my own. People toy with the idea of turning off sanity checks in production, but eventually reality sets in and they realize that this is a bad idea. Then they keep calling the sanity checks "ass
280.
▲
by
fdr
14y ago
I have found assertions very valuable in both Python and C. I have worked with code bases that both have them on in production and have them off in production, and the latter was generally the much more complex and more reliable system (it
281.
▲
by
fdr
14y ago
Disagree. D is but one language (which does not, in and of itself does not fill a vacuum), and I have serious doubts about the social situation regarding its compilers. However, I think it meets most of the other criteria. It also has a l
282.
▲
by
fdr
14y ago
I'm not sure if yet another person comparing their set of agreement/disagreement is useful, but here goes, because I like Go and think some people are skeptical about it with a bit too much enthusiasm because it either seems too hip (this o
283.
▲
by
fdr
14y ago
It is not only this: moving datums around in the database heap is expensive (invalidating caches, exacerbating thrashing) and touchy (index pointers, concurrency considerations). But debloating over time is an important property, so it's pr
284.
▲
by
fdr
14y ago
I would say that I have the exact opposite opinion of you: the manual is not so great at narration because it is really extensive. Consider the example you gave: the postgres tutorial makes no assumption that you can even connect to the da
285.
▲
by
fdr
14y ago
I think that's a very keen insight. There may be a detail that gets in the way, but nothing comes to mind at the moment. Did you know that PostgreSQL's referential integrity checks are -- in the most literal sense -- implemented as trig
286.
▲
by
fdr
14y ago
I basically agree with you, except in regard to documentation, of which I find exceptional in PostgreSQL, even compared to other database systems. Your toplevel comparison of the index of both manuals is not very informative to me. What
287.
▲
by
fdr
14y ago
I am speaking more generally -- I'm not evaluating a new database for my toolchain at the moment, and to be honest, I am very shy of anything that is proprietary-only. However, I thought your ideas were interesting regardless, so I felt co
288.
▲
by
fdr
14y ago
If I had any feedback, it might be to produce a frank document of trade-offs in your system: workloads that work very well, pathological workloads that perform poorly or lead to some awkward code, given the mechanisms at play. I'm sure you
289.
▲
by
fdr
14y ago
That limitation (not-lucid dependencies between contribs) is rather sucky, but jumping into the world of dependency management will require a deep breath for sure. Hence, instead of waiting for that, JSON support in un-adorned Postgres to s
290.
▲
by
fdr
14y ago
I see a lot of snarky comments (maybe that has to do with the journalism of the article), but my recollection of FoundationDB is that it is interesting. It's trying to tackle the problem of enabling ACID, while also not being SQL-dialect
291.
▲
by
fdr
14y ago
The last major web site update was in late 2004, according to my bisection of the wayback machine. It's a project, not a company, and there is no marketing or design budget. For example, Magnus, who does some Windows maintenance, is a pri
292.
▲
by
fdr
14y ago
I'm badly aching for this feature. Running log aggregation are such a pain when a statistical understanding of what is slow is as useful and extremely cheap (in terms of compute power) to gather. Adding some of the detailed information to
293.
▲
by
fdr
14y ago
I think a number of people might find such functionality useful -- every once in a while I run across people with tens or hundreds of thousands of schemas, because a program written to query against a particular schema is more convincing an
294.
▲
by
fdr
14y ago
For many small Rails web applications, details having sane (and rich) datetime support in the database is both nearly invisible (turning bugs into errors, and working about the same otherwise) and very useful. The same could be said about
295.
▲
by
fdr
14y ago
Also, if you add random Debian packages they are also entitled to run arbitrary programs (as root!) while installing. The only thing wrong about this title is that it does not read "https".
296.
▲
by
fdr
14y ago
I'd say that all in all that multi-master is still generally pretty hard to use -- there are packages that do work very well (consider the .org registry, which is slony), but I can't really say with conviction that they are cohesive and e
297.
▲
by
fdr
14y ago
I agree with you. I'd like to expand a little: The main people who can get a benefit from database independence are those who ship software to a client site to be executed. Imagine if you wrote some kind of accounting software package that
298.
▲
by
fdr
14y ago
Yes. At least, as-implemented.
299.
▲
by
fdr
14y ago
Well, PostgreSQL is a project -- not a company. As a project, it is very roughly run by consensus, and that means acting strategically is not something the project as a whole does very much. Sure, there are many project goals, but they're
300.
▲
by
fdr
14y ago
I think XC is a shared-nothing but globally consistent system. This lets you get some scaling up to a handful of nodes (maybe, charitably, a dozen...or two or three dozen), but as something that gives you ACID it is bound to have contentio
More ›