24th September 2020: PostgreSQL 13 Released!

Open Technology Group, Inc. announces expansion into California

Posted on 2006-06-09

In response to an increased demand for its open source training products, the Open Technology Group, Inc. announced today its expansion into markets in Northern California, "Our offerings in

the California market are in direct response to interest generated by our customers and partners

in that market space", said Chander Ganesan, President. "We see a growing need for qualified and structured open-enrollment, open source training programs - a need that is not currently met by experienced providers in that market. Following our initial offerings, we anticipate offering an expanded class schedule of our most popular courses in that market."

The Open Technology Group has scheduled its first open-enrollment course, PostgreSQL Administration, in Santa Clara, CA for the month following the Linuxworld San Francisco conference.

PostgreSQL - the most advanced open source database in the world - is heavily used by enterprises looking for a cost effective, scaleable, reliable, and feature-rich database platform. As a cost-effective replacement to commercial products, such as Oracle, DB2, Informix and MS SQL Server, PostgreSQL has seen widespread adoption and increased market penetration in recent years.


Founded in 2004 by experienced Open Source instructors with over a decade of experience, the Open Technology Group, Inc. (OTG) has established itself as the leading provider of training solutions centered about Open Source software and solutions. With its comprehensive library of in-house developed intellectual property, OTG is able to deliver comprehensive, customized, and structured training covering a wide range of software solutions. The Open Technology Group offers affordable customized on-site technology training throughout the world, as well as public-enrollment courses in both Morrisville, NC and Santa Clara, CA. For more information, and a complete course catalog, visit us online at

This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.