» tagged pages
» logout

(Feed found, click Add Page to syndicate.) Error finding feed, please try again » Find feed title

A Blog Page allows you to add entries, for news or other time sensitive postings

(Login required to save to your tagged pages.)
(or Cancel)

Make further edits, (or Cancel)

(Login required to save to your tagged pages.)
(or Cancel)

(Editing anonymously: to be credited for your changes, login or register a new account)

Change Page Permissions? Changing these permissions will adjust who can modify this page.

Anonymous (change)
Swik Users (change)
(or Cancel)
Upload an image from your computer:
or Copy an image from a URL:
or Erase the current icon:
Icon Preview:

or Cancel

Erase PostgreSQL? The contents of PostgreSQL page and all pages directly attached to PostgreSQL will be erased.

or Cancel

(Editing anonymously: to be credited for your changes, login or register a new account)

other page actions:
PostgreSQL

PostgreSQL

Tags Applied to PostgreSQL

3 people have tagged this page:

PostgreSQL is a Object-Relational DBMS supporting almost all SQL constructs, including subselects, transactions, and user-defined types and more. The name comes from the fact that many of the original developers also worked on Ingres, and so this is the “post-ingres” database. Design for the system began in 1986, with an explicit goal of providing a database that completely supported types with the minimum number of features necessary. By the early 1990s, the database had reached a significant number of users. Around this time, its status as a University of California, Berkeley project ended, but due to the open source license, development continued, as it does to this day.

PostgreSQL is seen as the most popular open source database after MySQL, although it has in many ways more advanced and more mature implementations of key features, particularly those required by heavy-duty OLTP applications.

Useful links:

An overview of features.

Frequentlyl asked Questions

www.postgresql.org
Numerous

sorted by: recent | see : popular
Content Tagged PostgreSQL

Log Buffer #107: A Carnival of the Vanities for DBAs

Welcome to the 107th edition of the Log Buffer. My name is Keith Murphy and I am a MySQL database administrator for the Pythian Group. In addition, I am the editor of MySQL Magazine. This is my second go for the Log Buffer, so I must be doing something right!

This week for the open source world brings OSCON in Portland Oregon. There are plenty of MySQL people present and there have been more posting this week from these realms than normal. Also, Lewis Cunningham, among others, posted news that EnterpriseDB released the results of their open source survey at OSCON. The 451 CAOS Theory published their thoughts on the survey.

Of interest to all DBAs is John Duncan’s post about what is called the “five minute rule”. This was introduced in 1987 by Jim Grey. And finally, before we dive into the specific server news, here is a post on Facebook’s project to build a distributed database similar to Google’s BigTable.

MySQL News:

Friday saw the release of the summer issue of MySQL Magazine. The highlights of the issue include the first annual MySQL Usage Survey. The magazine is available here. Peter, over at Percona, shows some initial benchmarks for the latest version (0.9.8) of Sphinx. If you aren’t familier with Sphinx, it is a full text search engine that easily integrates with MySQL.

Probably the biggest news this week was the announcement by Brian Aker of “Drizzle”. It is what amounts to a slimmed down version of MySQL server. These comments are from his initial post “Stored Procedures, Views, Triggers, Query Cache, and Prepared Statements are gone for now.” Interesting. My co-worker, Sheeri K. Cabral, posted a video of Brian Aker talking about the Drizzle project at this week’s OSCON. Monty Widenius writes a good summary how Drizzle can/might integrate with the MySQL “ecosphere” at large. It was very good to hear Monty say that Sun management is encouraging this project. There has been some other interesting posts about this as well including Arjen’s thoughts, and Paul McCullagh’s. Brian Moon gives a very thoughtful view on how Drizzle could potentially fit in at dealnews. While I could probably fill up the entire Log Buffer with links to post about Drizzle, I better leave it at that.

(more…)

MySQL: Planet MySQL

Jignesh K. Shah: Customer Feedback about PostgreSQL


During the course of last year, I did have opportunities to talk to
various Sun Customers about PostgreSQL. One of the thing I want to list
out the common problems that I heard from them which may not be really
trends but at least the one that I was "hit"  from customers while doing my job. [Read More]

PostgreSQL: Planet Postgresql

PostgresDAC installer bug hotfix

PostgresDAC is highly recommended for update due to the bug found in the installation program (client libraries were not accessible for LoadLibrary function, thus PostgresDACxxx.bpl package failed to load into IDE).

PostgreSQL: PostgreSQL News

MySQL vs. PostgreSQL

We were at the Sun+Zend party last night, and it was a blast (thank you Jesse Silver!). If you’re a PostgreSQL or MySQL user/developer or just a general database geek, you should’ve been there. Why?


(watch the video if its stripped in your feed reader)

Monty Widenius (MySQL) and Josh Berkus (PostgreSQL), decided to start sumo wrestling! It ended with a 5-0 score, advantage MySQL.

An attendee Tim Moore twittered: “Postgres is totally losing the sumo match. I’m migrating all of my databases to MySQL tomorrow.”

Monty says, this is what we do to people that leave Sun! In fact, if you didn’t already know, Josh Berkus, my esteemed colleague in the Database Group at Sun Microsystems, is leaving his post as the PostgreSQL Team Lead. We met for the first time, face to face at foss.in last year, and all I can say is I’m truly saddened to see him leave. But thanks to the magic of the open source world, we’ll still be interacting, I’m sure. Good luck Josh! (and better sumo practising next time, mmmkay?)

MySQL: Planet MySQL

Jignesh K. Shah: PostgreSQL/OpenSolaris Success Story

A new success story about a Sun Customer using PostgreSQL and OpenSolaris has been published. [Read More]

PostgreSQL: Planet Postgresql

Open Source Databases Comparison - Encore - ENCORE

PostgresSQL 8.2, MySQL 5, Derby 10.3, and HSQLDB 1.8 in terms of their limitations and strength

open-source: del.icio.us tag/open-source

Joshua Drake: PostgreSQL leads OSCON again

For the what seems like yet another year (can't we slow these guys down?), OSCON has proven to be the PostgreSQL stomping ground. Per our usual supply of great community members including, Selena, Gabrielle, Michael, Greg, Robert and the other Robert we had what seemed liked an endless supply of quality support and community reaction to all comers.

PostgreSQL: Planet Postgresql

Robert Treat: Certified Schizophrenic

The other night I was having dinner with a bunch of folks, and I think it was Jacob Kaplan-Moss (Django dude and Postgres user) who noted that the Postgres community's governance model was this crazy mix of distributed peer-to-peer style chaos, that on it's surface wouldn't seem functional, but somehow seems to work really well for our project (my paraphrazation). It's hard to argue. We don't have a one true leader, and we don't have a corporate master. In fact, we're so multi-faceted, we actually have two names (minimum) for the project! At times, this is a really good thing. Listening to Mark Shuttleworth's keynote last night, and his pointing out that an important part of the future of open source is having choice not just at the software level, but as users, developers, and in economic circles as well; and you're happy to note Postgres is already very much there. Of course, I promised Momjian (the elder) I'd have some angst in this post, so let me ignore the benefits of this model and focus on something a little more negative.
Continue reading "Certified Schizophrenic"

PostgreSQL: Planet Postgresql

Reading between the lines of EnterpriseDB?s survey results

EnterpriseDB has announced the results (PDF) of its recent survey of open source database usage.

While the company understandably highlights the adoption of PostgreSQL for transaction-intensive applications and its high reliability and performance and scalability EnterpriseDB has done a pretty good job of presenting the results in an unbiased manner.

I couldn’t help feeling that some of the more interesting results are hidden at the end of or buried within EnterpriseDB’s write-up, or even missing entirely, however.

For example, right at the end of its report EnterpriseDB states that “eight three percent have yet to pay for the use of their open source database” which speaks volumes about both the challenge that open source database vendors face in converting users to paying customers and the opportunity that is open to them if they can find a solution.

The company also states that “a majority of respondents indicated that they used an open source database in order to migrate away from their use of Microsoft SQL Server and Oracle commercial databases” which is technically accurate but a little misleading. It further adds that “less than one percent indicated they moved off of IBM DB2 to an open source database. Microsoft SQL Server was the highest at eleven percent while Oracle was at six percent.”

EnterpriseDB doesn’t tell us how many migrated from ‘other databases’ (which was the other answer available) but I think it’s fair to say that the majority of respondents in fact indicated that they had not used an open source database in order to migrate away from a proprietary database.

This supports the results we saw in our own recent open source database report as well as recent results from a Forrester survey. As I told eWeek in response to that survey, “Even EnterpriseDB, which offers proprietary Oracle-compatible functionality on top of PostgreSQL, is pitched more at Oracle avoidance projects than Oracle replacement projects.”

Back to EnterpriseDB’s survey, and Sam Dean at OStatic has questioned the finding that “only nine percent of respondents said they prefer commercial databases to open source ones”. The answer lies in the question being asked, which was “What prevents you or your company from using an open source database?”.

Clearly the result Sam mentions doesn’t mean that 81% of respondents prefer open source databases, but it does mean that only 9% have a preference for commercial databases that would prevent the use of open source databases.

While 85% indicated that “nothing prohibits their company from using an open source database” likewise that doesn’t mean that 85% are actually using an open source database.

Unfortunately EnterpriseDB didn’t share the result of the question “Have you ever used an open source database in your job or company?”. In the context of this survey, that’s a pretty significant result to leave out.

MySQL: Planet MySQL

Page 1 | Next >>
Username:
Password:
(or Cancel)