Slashdot Mirror

← Back to Stories (view on slashdot.org)

.org TLD Now Runs on PostgreSQL

Posted by ryuzaki0 on from the enterprise-ready dept.

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."

3 of 379 comments (clear)

  1. Wasn't Oracle, actually by kschendel · · Score: 5, Informative

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

  2. Re:This is a great performance test by bob@dB.org · · Score: 5, Informative
    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.

    --
    Acts@core.mailboks.com Acrux@core.mailboks.com Adam@core.mailboks.com Adar@core.mailboks.com Ada@core.mailboks.com
  3. .. You are, but the real problem is... by Anonymous Coward · · Score: 5, Informative
    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