.org TLD Now Runs on PostgreSQL

johnnyb writes "The .org domain, which has long run on Oracle systems, is now being transferred to a PostgreSQL system. I guess we can now dispel the "untested in mission-critical applications" myth."

Comments

not that impressive

[LinuxCumShot]

.ca runs on MS-DOS running some home brew DB that is just a bunch of batch files

Oracle...

[killthiskid]

"No one ever got fired for selecting Oracle, so we asked ourselves, Do we take that option?" he said.

Not true! I know someone who got fired for choosing oracle, then being unable to properly implement it.

Well, what are/aren't they using it for?

[etcshadow]

Because they don't take context or purpose into account at all. There are things that Postress may be better for and things that Oracle certainly shines at. I mean, hell, I love MySQL, too, but I wouldn't want to use it as the backend for _my_ system. Not that the others are hollisticaly "bad", it's just that Oracle is the most appropriate for this situation.

What's a TLD doing with a database? Making ridiculous numbers of extremely lightweight queries, and managing redundancy. That's not necessarily the same thing that everybody wants an "enterprise class" "tested" database to do for "mission critical" tasks.

Overkill.

[grub]

All they need is netcat, shell scripts and grep.

Wasn't Oracle, actually

[kschendel]

Verisign runs the shared registry with Oracle, but the registrar-specific data was and still is stored using Ingres.

Um

[TekReggard]

"Mohan said the decision to award the contract to a vendor deploying PostgreSQL vindicates the database as a reliable, stable management system."

No, it simply means that its going to be tested in a larger environment and if it does well then they get to party and say "woohoo it worked!" and if it flops they're all gonna feel really stupid. It doesnt mean its stable at all. The common practice of paraphrasing "LOOK!! Someone is using our product so it MUST work perfectly." is actually quite disturbing.

Re:This is a great performance test

[bob@dB.org]

Now we get to see how PostgreSQL handles those 98 % of wasted inquiries from DNS servers that don't know .elvis is not a TLD.

org. is tld (top level domain).

. (dot) is the root.

the story on the wasted 98% was about the . (dot) root servers, not about a tld server. you (and sadly, too many others) should read rfc 1035.

.. You are, but the real problem is...

[Anonymous Coward]

You can vacuum any time without shutting things down. You don't even lock a table thanks to the wonderful MVCC. But..

The real problem with Postgresql, however, is that if you are doing lots of updates where the keys increase forever, the index files grow forever. You can, of course, drop and recreate them (which we do in a cron job), but in a real 24/7 environment you've got a real problem when your queries all turn into table-scans because the indexes aren't built yet.

Here is some more information (seeIndex Maintenance? )

The only option I know if is to have two sets of tables and swap between them.

-- ac at work

Right tool, Right job

[Anonymous Coward]

If I here those words again, I think my head will explode. I don't remember anyone saying to use a wrench for a hammer if you have both. When people argue these things, they are argueing that a tool is the right tool for a job. PostgreSQL is being argued to be a tool that can be used for enterprise jobs. Either confront that or not, don't just state the obvious. No one said PostgreSQL is the only database to use.

I here this everytime a programming language is mentioned too. Either say Java can't do what perl can, or Java is slower than perl and back those up. Don't say Java is good and Perl is good because everyone knows that.

I don't mean to take my frustrations out on you poor poster, it's just high time people realize that this is like argueing philips or flat-head. It should be a poll option because it's preference, not because there ever is a right or wrong database for a job. It's a choice. After this has been going for a while without problems, we can then proceed to choose PostgreSQL to save money or because we like it better than Oracle or DB2.

It's as annoying as:
1: In soviet russia, Vi>Emacs
2: ?
3: goatse.cx, "MOD PARENT UP"

Re:Great idea...

[sharkey]

You'll note Slashdot uses MySQL and is very happy.

You misspelled "real fucking slow".