Postgres stopped using OIDs for regular tables in version 8.1, many years ago. You can force the old behavior with default_with_oids, but no one does that anymore. OIDs haven't been needed for referential integrity in quite a while. Only the system tables still use them to connect tables on a typical server, which is mainly because those need to be read during bootstrapping before all the SQL features are available.

The pgAdmin developers agree, and have already started on a full rewrite in Python. The goal of having a GUI app that's cross-platform used to take tools like C++ and wxWidgets, and that's what the current pgAdmin III is written in. The new one doesn't need to be so low-level in its library use.

Oracle has features like Edition-Based Redefinition for this job. They are a lot more work for the simple job of transactional DDL.

There's an old but accurate at the time page comparing this feature across databases at Transactional DDL in PostgreSQL: A Competitive Analysis.

I live very close to the Baltimore distribution center. What they've done there is position it right in the middle of where all the major highways here intersect. You really can get to any other part of Baltimore in 25 minutes from there. I suspect they're going to limit this service to popular items in cities where the layout makes things feasible.

And today, after almost six years of reasonably reliable service, I'm starting to have my doubts about Dreamhost. Two nights in a row, I made minor changes to the configuration for my domains through their Web Panel, and the Apache server on their west coast shared hosting box died and never came back on its own. The first outage was 2.5 hours. This outage is ten hours and counting.

Anybody know a good shared hosting provider with better reliability? This latest failure brings them down to barely two nines YTD, not including scheduled maintenance.

I'm also using GANDI as my registrar. I'm reluctantly letting DreamHost provide DNS for one domain, and deferring part of another domain to their nameserver, but otherwise I've always preferred to keep my DNS servers in-house (literally), for maximum control. My primary is a Mac Mini, and my secondary is a Raspberry Pi.

I was using their shared hosting to serve images associated with my domain, with the HTML served from my home server over DSL—basically as a poor-man's Akamai. Unfortunately, what I found was that their site would randomly take the better part of a minute to respond to a request. That meant that sporadically it would take longer for them to serve an image than for me to do so from my home DSL connection, and pretty much the entire transfer time was spent waiting to get the first byte back from their server.

At some point, I decided to gather statistics on the problem by using a machine at work (typically approaching or reaching gigabit speeds) to make a very short request to the server every couple of minutes. I forget what percentage of those requests took more than half a minute to come back, but I'm pretty sure it was in the double digits.

Obviously, I got a terrible server that was badly configured and/or massively overloaded. Obviously that won't happen to everybody. The reason I left is that even after proving definitively that the server sucked, and requesting that my content be migrated to a server that wasn't overloaded, they refused to fix the problem. Every server provider will have problems now and again. What matters is how you handle them when they happen, or in this case, whether you handle them when they happen. GoDaddy didn't, and that makes them a terrible provider even if only a tiny percentage of their customers have problems, because you never know when you're going to find yourself in that tiny percentage.

No. "Apps featured in Google Play" isn't the same as "Featured Apps in Google Play". Neither phrase was from Google, either, but from the summary.

The summary is wrong in others ways, too. It says that Google is going to begin screening apps. The actual announcement says that this has been going on for several months. It also says that the process is "human-based", which the announcement doesn't say, just that the process "involves a team of experts who are responsible for identifying violations of our developer policies earlier in the app lifecycle." This leaves open the possibility that the team in question automates the actual screening, which is obviously much more normal for Google.

Really, your best bet is to ignore the summary and the linked article and just read the post from Google: http://android-developers.blog...

When you buy a house or flat in most countries you arn't allowed to absolutely anything you please with it.

Hey, there you go, appeal to everyone's undying love for homeowners associations to get your point across!

Except... it'd probably work better if they weren't so generally hated.

Besides that, you're probably fine with any of them. My GoDaddy experience can best be summed up as:

• On their hosting service, they limited all processes run by your user account (not just CGI) to a certain number of seconds. This made it almost impossible to upload large files, because they invariably timed out before the upload could finish.
• Despite that limit, the service was still unusably slow because of all the WordPress and PHPBB instances whose full-text searches stink on ice. Requests to move my (purely static) content to a server that wasn't so bogged down were denied.
• Then, I tried to buy a cert from them. After I made the purchase, but before it actually became available for me to retrieve, they cancelled the purchase and told me that they no longer offered the number of years that I'd bought, despite the fact that I bought it using publicly available links on their website.

Let's just say I ditched them within the first month, and we'll leave it at that. I switched to DreamHost, and haven't looked back. Their service isn't perfect performance-wise, but it is so much better than GD that it isn't even funny. (Yes, I know you're just asking about domain registration, but lots of folks do one, then the other, so....)

And whatever you do, don't get your hosting from the same company that provides your domain names. There are far too many horror stories of hosting-related disputes leading to frozen domain names.

Deep Neural Nets will use it, at least the very big, wide, deep ones will.

Sssh! You're not supposed to tell him he's on the GCHQ honeypot!

Sounds like my daily commute. WORKSFORME WONTFIX.

Actually, Mastercard and Visa aren't even companies. They're associations of banks. There are incorporated entities under those names (many of them, actually, one per country, plus Mastercard International and Visa International, which themselves have many national subsidiaries), but they don't issue credit cards, and only operate some pieces of the transaction processing networks.

As someone who regularly meets with representatives from both, discussing areas where the competitors are trying to collaborate on standards but without giving up any edges, I call bullshit on this claim. They're most definitely separate, and competitors. It is true that their interests align in some cases, and they work together almost as much as they compete, but your claim that they're the same company is just ludicrous.

Google doesn't use the ID verification data for anything else. Actually, it's not clear what it would be useful FOR. How does knowing your driver's license number help Google to decide what ads to show you?

Plus, the vast majority of users of Google Wallet don't have to submit this data. It's not the normal case.