fdr

74 ms·

301.
by fdr 14y ago
You and I sound like we may be cut from similar cloth. I find Go's approach to error handling -- which is to not to do much about the problem at all -- is better than pervasive use of exceptions but worse than some other possible mechanism
302.
by fdr 14y ago
True to forgettable SQL-ish (did you know that indexes are not addressed by the SQL standard?) syntax, I got it slightly wrong: $ psql fdr=> \h CREATE INDEX Command: CREATE INDEX Description: define a new index
303.
by fdr 14y ago
It is not entirely brand. For me, I only begrudgingly use a Macintosh laptop because it is better for someone who doesn't want to fiddle, now or in future releases of their distribution. At this point given the length of time I've stuc
304.
by fdr 14y ago
> PostgreSQL also supports concurrent index creation I use this all the time, and am flabbergasted how people can do without it. I feel like migration frameworks should make it the default with Postgres. It's too bad it can't be mixe
305.
by fdr 14y ago
> It does not take locks, other than for very briefly. You are right. I think this is a misunderstanding in the original material: if one does not use a default expression (i.e. the default is NULL) then the implementation they are u
306.
by fdr 14y ago
Also look at GIN. Although the documentation claims it is typically larger than GIST, in certain cases (a small lexeme set, which is not true in the general case full-text) it can seem to be smaller and faster. Mostly this can be true ove
307.
by fdr 14y ago
Speaking of backups, you might want to run wal-e: https://github.com/heroku/wal-e It is not the best program I ever principally authored (since I know you are very discriminating Python programmer), however, it does work very well and has
308.
by fdr 14y ago
I agree with you, but I think that is because we both tend to walk a lot. Fast moving vehicles (generally bicycles and skateboards) in foot traffic are a damn menace. But I can see how in the vast empty sidewalks of some suburbs that ridin
309.
by fdr 14y ago
I saw someone else have a bad reaction to this statement, but I might be to blame for this. See: http://news.ycombinator.com/item?id=4062983 But let me try to frame it more carefully: at the time (and maybe still) a lot of providers expe
310.
by fdr 14y ago
I more or less disagree. My main frustration with Linux For Personal Use is that I can't buy a piece of hardware that I know won't regress with new versions of a distribution for three plus years or get any service if it does. My referenc
311.
by fdr 14y ago
That's correct, but it's not really incremental. It's all or nothing at the time you run it, even though it is a relatively small downtime because it twiddles catalog (corner case: statistics need to be regathered, of which we have a gross
312.
by fdr 14y ago
It also provides a stable, preassigned OID. Because extensions don't really handle dependencies yet, this is critical -- making the extension "foo" that depends on the extension "json" is still rather far away. That means projects like plv
313.
by fdr 14y ago
These are some of the usual options, but one hopefully one day there will be logical replication so one can do it incrementally and on-line.
314.
by fdr 14y ago
I think Jeff was principally referring to relational dogma that is so prevalent in other SQL database system culture, even though they might implement such types to get a check-box (or not: MSSQL doesn't support arrays, AFAIK) Clearly ne
315.
by fdr 14y ago
This is a procedural function, which is a pain in the butt, and slow. MERGE support has been a want-to-have for a long time. Unfortunately Postgres is stuck between the complex but useful behavior of implementing MERGE (without destroying
316.
by fdr 14y ago
I think it is completely non-silly. Debian was very simply and to the letter of the law in violation of the terms under which a piece of software can be called Firefox, and at any time Mozilla Corporation is entitled to bring civil action,
317.
by fdr 14y ago
I can't give you a comparison, but for what it's worth, it is used on the Postgres documentation and mailing list archives. I mention this because you can play with it and get an intuitive sense of its performance and subjective usefulness
318.
by fdr 14y ago
Given the audience that'd buy this software, I doubt that just dropping in a LICENSE file -- which is all that is needed -- will materially impact this borderline scam. Unlike the 4-clause BSD, which was not tractable, the modern 3-clause
319.
by fdr 14y ago
A more detailed set of articles about this are in a large spread from The Economist a little while back: http://www.economist.com/node/21552901 Considering the boldness of the economic claims, it fills in a little more background and nece
320.
by fdr 14y ago
> The reason is it's much faster to query memcached directly without even opening database connection. Sometimes you need to augment data in a SQL database with memcache information, and then subsequently compute a predicate, and it wou
321.
by fdr 14y ago
I think this MySQL feature has the potential to be neat, but if one is using it in the mode where one persists or faults to disk it seems like the biggest feature will not be performance, but protocol-compatibility and ease of development a
322.
by fdr 14y ago
w.r.t "useless": Joins against memcached data, and expiry of keys via trigger. Different, yes, useless -- well, up to you. Not written for no reason, though.
323.
by fdr 14y ago
One might choose to use the array datatype, combined with GiST, GIN, and/or expression based indexes, depending on the workload. That would be somewhat more lucid in most situations than a string packed into an attribute.
324.
by fdr 14y ago
To that mind, the post has been amended to drop support for that one extension. Unless you have a great use case, it seems like the consensus is "do not use chkpass". pgcrypto should have everything one needs and probably a few more thing
325.
by fdr 14y ago
A number of my coworkers use Unity, and I do too. We're all programmers. Other than it being frustratingly buggy and with a klunky visual design, the general consensus is "meh, went better than I expected". Granted, programmers have a simp
326.
by fdr 14y ago
> It's not architecturally impossible for us to support long-running read snapshots, but it is expensive for our storage servers to keep snapshots alive for a long time. So our backup solution instead works by backing up transaction log
327.
by fdr 14y ago
Sure it is. But I would say, more to the point, it's a problem for systems that support consistent snapshots. The question is: how does it deal with the failure condition?
328.
by fdr 14y ago
Yes. But then the data is not available or other transactions will fail to commit during a long backup operation, and most people don't like that.
329.
by fdr 14y ago
It is not complex, but it is very burdensome, usually because various garbage collection processes cannot act as long as the long snapshot is open.
330.
by fdr 14y ago
Ah. So that probably means a consistent copy or backup is probably practically impossible.

More ›