PostgreSQL on SWiK

Postfix PostgreSQL Howto

Fri, 29 Aug 2008 13:52:07 -0700

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

Fri, 29 Aug 2008 10:56:24 -0700

Welcome to the 112^th edition of Log Buffer, the weekly review of database blogs.

First, thanks to last issue’s contributors–Joe Izenman, Dan Norris, and Jason Massie–for snatching victory from the jaws of defeat and making LB#111 a worthwhile read. That’s what it’s all about!

Oracle’s up first, starting with our old friend Doug Burns and his Time Matters series, in which he holds up to the light the concept of DB Time: “. . . [the] total time spent by user processes either actively working or actively waiting in a database call.” He continues, “There’s a lot more I could say about DB Time. Like all of the best performance concepts or methods (e.g. YAPP, Method-R) it can seem so obvious as to not be worth saying, but contains an enormous amount of common sense and technical rigour.”

Arup Nanda writes about the time he spent Diagnosing Library Cache Latch Contention. About half an hour, as it happened, but he’s a real pro, and his analysis just goes to show. To quote, Nuno Souto–who makes the best blog endorsements– “Damn useful stuff . . . bookmarked.”

Tanel Poder has another script for you to fall in love with, which makes its debut in flexible sampling of any V$ or X$ view with sample.sql. It is, writes Tanel, “ . . . a simple but powerful sqlplus script for ad-hoc sampling of any V$ view.”

Kenneth Downs, the Database Programmer, offers Advanced Algorithm: Sequencing Dependencies, a smart look at satisfying dependencies in databases. What does that mean? Well for example, Kenneth writes, “All popular Linux distributions have a package installation system in which each package lists its required dependencies. If you want to install a large number of packages in one shot, producing a tangled bunch of related dependencies, today’s algorithm can be used to work them all out.”

That’s the kind of task for which we humans use tools like mind maps. Jason Arneil shares his ASM Mind Map.

Laurent Schneider went off-road and came back something not on the map at all: the difference between rollbac and rollback.

(more…)

JBossWiki : SetUpAPostgreSQLDatasource

Fri, 29 Aug 2008 02:59:42 -0700

JBossWiki : SetUpAPostgreSQLDatasource

Fri, 29 Aug 2008 02:56:51 -0700

Pavel Stehule: updatable cursor's test

Fri, 29 Aug 2008 02:51:03 -0700

Hello

I had to update every row of table with an result of external function. It was possibility for testing of some patterns:

postgres=# create table testcursor(i integer primary key, v integer);
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "testcursor_pkey" for table "testcursor"
CREATE TABLE
postgres=# insert into testcursor select i, 0 from generate_series(1,100000) g(i);
INSERT 0 100000
postgres=# analyze testcursor;
ANALYZE

/* external function sample */
create or replace function ext_fce(a integer, b integer)
returns int as $
declare r int;
begin
/* protect section */
begin
  r := b;
exception when others then
  r := null;
end;
return r;
end;
$$ language plpgsql;

1. test - standard update statement

postgres=# update testcursor set v = ext_fce(i, 30);
UPDATE 100000
Time: 4369,246 ms

2. test - update with updateable cursors

create or replace function testc2(_v integer)
returns void as $$
declare
c cursor for select i from testcursor;
_i integer;
begin
open c;
fetch c into _i;
while found loop
  update testcursor set v = ext_fce(_i, _v)
    where current of c;
  fetch c into _i;
end loop;
close c;
end;
$$ language plpgsql;
postgres=# select testc2(20);
testc2
--------

(1 row)

Time: 8434,985 ms

3. test - update with PK

create or replace function testc3(_v integer)
returns void as $$
declare _i integer;
begin
  for _i in select i from testcursor loop
    update testcursor set v = ext_fce(_i,_v) where i = _i;
  end loop;
end;
$$ language plpgsql;
postgres=# select testc3(30);
testc3
--------

(1 row)

Time: 9959,209 ms

Result: Using updateable cursor is about 90% slower than one statement. Usig pk is about 17% slower than updateable cursor. - So updateable cursors has sense and it is well to use it. But every iteration is much slower than one statement's update.

Home - Continuent

Thu, 28 Aug 2008 23:56:29 -0700

Selena Deckelmann: Leaving US PostgreSQL Assoc. - what’s next for me?

Thu, 28 Aug 2008 19:51:06 -0700

image credit to bugbunnybambam

A few weeks ago, I decided to resign from the United States PostgreSQL Association board. Shortly after, I left for a long vacation where I thought about what I wanted to do next - both professionally and in a volunteer capacity.

Looking back, I started volunteering for PostgreSQL two years ago. I’ve led PDXPUG, staffed many conference booths, given nearly a dozen talks and run conferences. Of the work I’ve done, I’ve been most surprised by the creation of the PUGS website and all the user groups that followed.

This may sound silly - but I was so incredibly proud to see user groups in Oklahoma, Toronto, Los Angeles and the D.C.-area (BWPUG) hold meetings, share their experiences and publish fantastic presentation slideshows. All while I was out of the country!

That’s a true sign of success to me: groups of people leading themselves and sharing their knowledge with each other. It’s open community, with minimal bureaucracy, and (I hope) maximum fun.

With that in mind, I’ve decided to make this next year’s volunteer work focused on a simple idea:

Enable people to connect and learn directly from each other.

So what you can expect from me over the next year is more of the same, but now with that end goal in mind: more PostgreSQL user groups (for as long as the postgresql.org folks would like me to stay), more ways to connect people directly to each other, more authentic community building through un-conferences, and more contributions - through code, testing and presenting of that work.

To give you an idea — here’s what I’m up to over the next couple of months:

Linux Plumber’s Conference, September 17-19 - with Gabrielle Roth, we’ll be presenting information about databases (PostgreSQL specifically) and filesystem performance using data gathered from the recently installed PostgreSQL performance lab.
PostgreSQL Conference West, October 10-12 - I’m not organizing this year, but I’m organizing a session on hacking PostgreSQL, led by some PostgreSQL hackers!
WhereCampPDX, October 17-19 - I’m helping organize this un-conference for geography-specific tech - practicioners, professionals, enthusiasts, artists! We’ve got some great ideas and hope to publish details in the next week about the awesome folks involved, the venue and the parties!

Hope to see you at these events!

–

I haven’t talked about my work much in this blog, and probably will continue not to do that much here - but I also wanted to share that I’ve taken a position with End Point Corporation, a fantastic company that works on open source software, and provides support for PostgreSQL. I’ll be focusing on PostgreSQL, and doing a little Perl development here and there.

Bruce Momjian: What Do You Do?

Thu, 28 Aug 2008 18:51:01 -0700

Last week I got three questions about what I do for a living, and from people who have known me for years. I assume other Postgres and open source people often get the same question; which got me thinking, why is it so hard to explain?

Bruce Momjian: TODO TO-Gone

Thu, 28 Aug 2008 18:51:01 -0700

The TODO list has been removed from Postgres CVS and converted to a wiki. This will allow more people to maintain it, as they have done with the commit fest pages.

Frank Wiles: Fret Free -- Introduction to Django and the Django Software Foundation

Thu, 28 Aug 2008 18:51:01 -0700

LinuxPro Magazine just released my latest article, an introduction to Django and some discussion about the newly created Django Software Foundation. Being a life long Perl user, I didn't think I would enjoy Django at all. I have to admit that it is a VERY polished system. It has great PostgreSQL support, in fact the core developers smartly prefer it over MySQL for their own systems.

You can download a PDF copy of the article at, Fret Free -- Django and the Django Software Foundation. The print issue will hit the stands in October. Hope you enjoy it!

Robert Lor: Setting up Drupal with PostgreSQL on OpenSolaris 2008.05

Thu, 28 Aug 2008 18:51:01 -0700

Drupal is quickly gaining popularity among the many Open Source Content Management Systems (CMS) out there. AFAIK, Drupal is mostly used with MySQL on Linux, so I wanted to find out myself how easy (or hard) it is to get it working with PostgreSQL on OpenSolaris. Below were the steps I followed:

Install OpenSolaris 2008.05. The installation from the Live CD went very smoothly, much simpler than previous versions of Solaris. Great job to the installer team! If you don't have the CD, you can download it from http://www.opensolaris.com/. Remember, OpenSolaris comes with the bare minimum, so additional software need to be installed from the network repository.

Install Web Stack (Apache, PHP, MySQL, etc). After the OS installation, I fired up Firefox and just followed the instructions from the Welcome Page, clicked on "the world of OpenSolaris" link and that took me to http://www.opensolaris.com/learn/. From there, I followed these links: "Web Stack Getting Started Guide" > "2. Getting Started" > "Installing Web Stack Components" > "Setting Up Your AMP Development Environment". I decided to install everything using the following command.


# pkg install amp-dev

Initialize the Web Stack Environment & Start Apache. To do this, I just followed the Web Stack Getting Started Guide. Clicked on Applications > Developer Tools > Web Stack Getting Start Guide, and did the followings:

Initialize the environment: Clicked on Applications > Developer Tools > Web Stack Initialize

(The guide is a bit confusing, so run the following commands first before starting Apache/MySQL; otherwise you'll get errors)
# svccfg import /var/svc/manifest/network/http-apache22.xml # svccfg import /var/svc/manifest/application/database/mysql.xml

Start Apache & MySQL: Clicked on Applications > Developer Tools > Web Stack Admin > Start Apache2/MySQL servers

Point browser to http://localhost so check that Apache is running.

Install PostgreSQL. I wanted to install PostgreSQL 8.3 from the network repository, but I found out that 8.3 didn't make it to OpenSolaris 2008.05 which was based on Nevada build 86. To see all the available PostgreSQL packages, run.

# pkg search -r postgres
The output shows a lot of packages, but unfortunately the 8.3 packages are for later builds of Nevada. I did try to install one package, but it didn't work.

I could build Postgres 8.3 myself, by fortunately Sun also provides the binary in tarball format at http://www.postgresql.org/ftp/binary/v8.3.3/solaris/opensolaris/i386/, so I just used this version.
Setup PostgreSQL. I wanted to run Postgres using using the "postgres" user, but it's setup as a role by default, so I did the following to change it to a normal user:
a) As root, run "passwd -d postgres"
b) Edit /etc/user_attr and change the type for "postgres" from role to normal
c) Change the home directory and shell for "postgres" using the usermod command

Now I need to create the Postgres DB cluster. Make sure the directory where Postgres is installed is added to PATH.
postgres$ initdb -D /directory/path/to/data
Install Drupal 6.4. Follow the instructions in INSTALL.txt and copy the files to /var/apache2/2.2/htdocs.

Follow the instructions in INSTALL.pgsql.txt to setup the database. Here's what I did. Make the Postgres is running.
postgres$ createuser --pwprompt --encrypted --no-adduser --no-createdb drupal Enter password for new role: Enter it again: Shall the new role be allowed to create more new roles? (y/n) y postgres$ createdb --encoding=UNICODE --owner=drupal drupaldb
Configure Drupal. Make sure Apache is running and point the browser to http://localhost, and you should see the Drupal setup page.

That's it. Besides a couple of small hiccups, I think the whole process was quite straightforward.

Devrim Gündüz: From 3067 hits to 34538 hits

Thu, 28 Aug 2008 18:51:01 -0700

It's been about 8 months since I started PostgreSQL RPM repository project. Every month, we got more hits, more hits. When we first started project, we got 3067 hits per day. This month, we have an average of 34538 hits per day. That is amazing. Also, the PostgreSQL Live CD has been downloaded more than 1000 times.

I hope this repo helps people to deploy and use PostgreSQL easily.

Devrim Gündüz: Lazy bloggers

Thu, 28 Aug 2008 18:51:01 -0700

We have some lazy bloggers in Planet PostgreSQL -- would you like to post something before I blog your names?

David Fetter: PostgreSQL Weekly News - August 24 2008

Thu, 28 Aug 2008 18:51:01 -0700

PostgreSQL Weekly News - August 24 2008
PostgreSQL Product News
Archiveopteryx 2.1.1 and 3.0.0 will be out soon.
http://aox.org/
PostgreSQL Jobs for August
http://archives.postgresql.org/pgsql-jobs/2008-08/threads.php
PostgreSQL Local
PGCon Brasil 2008 registration is open.
http://pgcon.postgresql.org.br/inscricoes.en.html
Stefan Kaltenbrunner is giving a talk about monitoring strategies for
postgresql.org at the Nagios conference 2008 September 11-12 in
Nuremberg, Germany.
http://www.netways.de/nagios_konferenz/y2008/programm/v/postgresql_monitoring/
The Prato Linux User Group will be having PostgreSQL talks in
September. The schedule in Italian is:
http://www.prato.linux.it/serate_a_tema_2008
PGCon Brazil 2008 will be on September 26-27 at Unicamp in Campinas.
http://pgcon.postgresql.org.br/index.en.html
PgDay.fr will be October 4 in Toulouse. The Call for Papers is open:
http:www.postgresqlfr.org/?q=node/1686
Registration:
http:www.pgday.fr/doku.php/inscription
The Open Source Day in Magdeburg, Germany will be on October 11 2008.
http:www.open-source-tag.de/
Send in your interesting talks for the PostgreSQL track!
The call for papers is open until August 31 2008.
http:www.open-source-tag.de/cfp/index.html (in german)
PostgreSQL Conference West 2008 will be October 10-12 at Portland
State University in Portland, Oregon.
http:www.postgresqlconference.org/
Talk submission at:
http:www.postgresqlconference.org/west08/talk_submission/
Sponsor the European PGDay!
http://www.pgday.org/en/sponsors/campaign
The Call for Papers for European PGDay has begun.
http://www.pgday.org/en/call4papers
PGDay.(IT|EU) 2008 will be October 17 and 18 in Prato.
http://www.pgday.org/it/
Continue reading "PostgreSQL Weekly News - August 24 2008"

Pavel Stehule: Using cursors for generating cross tables

Thu, 28 Aug 2008 18:51:01 -0700

I am working on procedure support in PostgreSQL more than one year. Missing procedures is one disadvantage of PostgreSQL. Because procedures are not called from SELECT statement, then it couldn't respect some rules like functions. Procedures are mainly used for explicit transaction controlling and for generating mutable results (like dynamic record set or stacked record set). Dynamic record set is interesting feature when we nothing know about result set's columns. It's typical for cross tables. Because PostgreSQL doesn't support procedures, we cannot return dynamic (mutable number of columns) queries directly, but we can return dynamic cursor. This method of generating cross tables is inspired by Roland Bauman's http://rpbouman.blogspot.com blog.
Cross table is based on query's pattern:

SELECT shop,
SUM(CASE gender WHEN 'f' THEN salary ELSE 0 END) AS f,
SUM(CASE gender WHEN 'm' THEN salary ELSE 0 END) AS m,
SUM(salary) AS total
FROM employees INNER JOIN shops USING (shop_id)
GROUP BY shop

for data:

CREATE TABLE employees (
id serial PRIMARY KEY,
shop_id int,
gender char(1),
name varchar(32),
salary int
);

CREATE TABLE shops (
id serial PRIMARY KEY,
shop varchar(32)
);

INSERT INTO shops(shop) VALUES('Zurich'),('New York'),('London');

INSERT INTO employees (shop_id, gender, name, salary)
VALUES
(1, 'm', 'Jon Simpson', 4500),
(1, 'f', 'Barbara Breitenmoser',4700),
(2, 'f', 'KirstenRuegg',5600),
(3, 'm', 'Ralp Teller',5100),
(3, 'm', 'Peter Jonson',4700);

I write function, that generate necessary SELECT statement and open dynamic cursor.

CREATE OR REPLACE FUNCTION do_cross_cursor(dimx_name varchar,
    dimx_source varchar, dimy_name varchar,
    dimy_source varchar, expr varchar)
RETURNS refcursor AS $$
DECLARE
col_list text[] := '{}';
query text;
r RECORD;
result refcursor := 'result';
BEGIN
FOR r IN EXECUTE 'SELECT DISTINCT '
  || dimx_name || '::text AS val ' || dimx_source
LOOP
col_list := array_append(col_list, 'SUM(CASE ' || dimx_name
 || ' WHEN ' || quote_literal(r.val) || ' THEN ' || expr
 || ' ELSE 0 END) AS ' || quote_ident(r.val) || '');
END LOOP;
query := 'SELECT ' || dimy_name || ', '
 || array_to_string(col_list, ',')
 || ', SUM(' || expr || ') AS Total '
 || dimy_source || ' GROUP BY ' || dimy_name;
OPEN result NO SCROLL FOR EXECUTE query;
RETURN result;
END;
$$ LANGUAGE plpgsql STRICT;

Because cursors should be used only in transaction, I have to use explicit transaction:

BEGIN;
SELECT do_cross_cursor('gender', 'FROM employees','shop',
     'FROM employees e JOIN shops s ON s.id = e.shop_id',
     'salary');
FETCH ALL FROM result;
END;

BEGIN;
SELECT do_cross_cursor('shop', 'FROM shops','gender',
      'FROM employees e JOIN shops s ON s.id = e.shop_id',
      'salary');
FETCH ALL FROM result;
END;

There is result:

postgres=# BEGIN;
BEGIN
postgres=#   SELECT do_cross_cursor('gender', 'FROM employees',
  'shop',
  'FROM employees e JOIN shops s ON s.id = e.shop_id', 'salary');
do_cross_cursor
-----------------
result
(1 row)

postgres=#   FETCH ALL FROM result;
 shop   |  m   |  f   | total
----------+------+------+-------
New York |    0 | 5600 |  5600
Zurich   | 4500 | 4700 |  9200
London   | 9800 |    0 |  9800
(3 rows)

postgres=# END;BEGIN;
COMMIT
BEGIN
postgres=#   SELECT do_cross_cursor('shop', 'FROM shops','gender',
 'FROM employees e JOIN shops s ON s.id = e.shop_id', 'salary');
do_cross_cursor
-----------------
result
(1 row)

postgres=#   FETCH ALL FROM result;
gender | New York | Zurich | London | total
--------+----------+--------+--------+-------
m      |        0 |   4500 |   9800 | 14300
f      |     5600 |   4700 |      0 | 10300
(2 rows)

postgres=# END;
COMMIT

Greg Smith: Linux disk failures: Areca is not so SMART

Thu, 28 Aug 2008 18:51:01 -0700

One of the most frequently asked questions on the PostgreSQL Performance list is "what disk controller works best with PostgreSQL?" It's a tough question; every product has different things it's good and bad at, and it can be hard to through all that to figure out what makes sense for your application. You need to focus equally on performance and reliability, as disk drives are very prone to

Pavel Stehule: default parameters for PL functions

Thu, 28 Aug 2008 18:51:01 -0700

Hello

I completed one task - defaults for PL functions. Using is simple - it is same as Firebird's 2.x defaults.

postgres=# create or replace function x1(int = 1,int = 2,int= 3)
        returns int as $$
          select $1+$2+$3;
        $$ language sql;
CREATE FUNCTION
postgres=# select x1();
x1
----
6
(1 row)

postgres=# select x1(10);;
x1
----
15
(1 row)

postgres=# select x1(10,20);
x1
----
33
(1 row)

postgres=# select x1(10,20,30);
x1
----
60
(1 row)

This is first step before named parameters feature - and less controversy. Second step will be difficult - there are two opinions about named parameter's syntax: variant a) using Oracle's syntax name => expression and variant b) use own syntax based on keyword "AS" expression AS name. I prefer variant @a - I thing so it's more readable (SQL use AS for labeling). Variant @b is safe from compatibility views. There was discussion on pg_hackers - without any conclusion. So I hope so at least defaults will be committed.

bye
Pavel

Greg Sabino Mullane: OpenSQL Camp 2008

Thu, 28 Aug 2008 18:51:01 -0700

This looks interesting: a community-organized database conference. Not just the Postgres community, but inclusive of all database communities as well (Yes, other database systems have communities as well, although none are as good as the Postgres one . From Baron's blog post:

Key facts:

It is of, by and for the community (you).

At this event, all open-source databases are created equal. We'll learn together and grow together.

It's a combination conference and hackathon.

It's free.

It is Friday night Nov 14, 18:00 through Sun the 16th at 18:00 in Charlottesville, Virginia USA in a very cool location.

The website, where all details will be posted: http://opensqlcamp.org/

The mailing group, where details will be discussed, decided and arranged: http://groups.google.com/group/opensqlcamp

Date, time and place are confirmed and will not change. You can make your travel plans now. There's travel information on the wiki.

We already have some great speakers who have offered to give great talks. These and other details will show up on the wiki as they're finalized.

Sponsors are needed. See the wiki.

Despite the name, this will be different from other Camp conferences you've been to. This is a combination of a planned event (with great speakers and sessions), semi-planned spontaneity (sessions to be decided by attendees the night before), and a hackfest. It's the best elements cherry-picked from all the conferences (and un-conferences) you've been to.

Jignesh K. Shah: Openbravo ERP on PostgreSQL/OpenSolaris 2008.05

Thu, 28 Aug 2008 18:51:01 -0700

Interested in setting up an ERP for your business which uses PostgreSQL? Here is an entry on how to install Openbravo ERP using PostgreSQL/OpenSolaris 2008.05 [Read more]

Robert Hodges: Answering Monty's Challenge: Advanced Replication for MySQL

Thu, 28 Aug 2008 18:51:01 -0700

Today Continuent is publishing the Tungsten Replicator, which provides advanced open source master/slave replication for MySQL. Publishing code is the first step to creating a robust alternative to current MySQL replication and will be followed by similar support for Oracle, PostgreSQL, and many other databases.

We started with master/slave replication on MySQL for a very simple reason: we know it well. And we know that while MySQL replication has many wonderful features like simple set-up, it also has many deficiencies that have persisted for a long time. Monty Widenius, a widely respected MySQL engineer, summarized some of the key problems last April:

- replication is not fail safe
- no synchronous options
- no checking consistency option
- setup and resync of slave is complicated
- single thread on the slave
- no multi-master
- only InnodDB synchronizes with the replication (binary) log

These issues are well-known to the MySQL community. Monty laid down a challenge, but we all know the community can write software that solves it. However, there’s a much bigger challenge out there. There are highly capable replication products produced by commercial vendors like Golden Gate, Quest, Oracle, Sybase, and others. They handle high availability, performance scaling, upgrade, heterogeneous replication, cross site clustering—you name it. Why aren’t these capabilities available in an open source product? Why doesn’t that open source product have the ease-of-use and accessibility MySQL is famous for?

The Tungsten Replicator is designed to answer that challenge. Here’s the initial feature set:

Simple set-up procedure
Master/slave replication of one, some, or all databases
MySQL statement replication
Proper handling of master failover in presence of multiple slaves
Checksums on replication events
Table consistency check mechanism

And here’s the roadmap:

Group communications-based management
Oracle support
PostgreSQL support
MySQL row replication
Heterogeneous replication
Multi-master via bi-directional replication with conflict resolution
Semi-synchronous replication
Parallel update on slaves to increase performance
Proxying support to reduce or eliminate application changes

We are implementing all of these features in a way that abstracts out platform and database differences. The architecture is not just database-neutral--by making it possible to extract from one database type and push to another we lay a cornerstone for heterogeneous data transfer.

Tungsten Replicator is available on our community website at http://community.continuent.com. Stop by and check it out. The code is in the early stages but will mature very rapidly. You can help us guide it forward. We are looking forward to answering Monty’s challenge and going much further. We are looking forward to creating something that brings powerful replication within the reach of every database user.

Bruce Momjian: The Kitchen Sink Has Arrived?

Thu, 28 Aug 2008 18:51:01 -0700

There has been much discussion within the Postgres community about having a kitchen sink distribution of Postgres that bundles the database server with the many plug-ins available for Postgres. We have had something similar for Windows since 2005 but not for other operating systems. Such distributions are helpful for new users and people wanting to experiment with Postgres and its external enhancements.

Devrim Gündüz: Keep informed about the latest updates for your distro

Thu, 28 Aug 2008 18:51:01 -0700

If you are using my rpm repository, you may also use its rss feed to keep informed about the latest RPM updates.

Just click your environment at RPM Chart, and subscribe to RSS feed (it is easy if you are using Firefox).

Yes, we aim to make your lives easier

Hubert Lubaczewski: Hunting “idle in transactions”

Thu, 28 Aug 2008 18:51:00 -0700

If you ever encountered “idle in transaction” connections, you most likely hate them. I know, I personally hate them. They interfere with most of “cool toys” like replication, vacuum, DDL queries. So, when I saw them on a database I was looking on, I decided to act. Easier to say, difficult to do. How to fix the [...]

Continuent Joins Intel® Certified Solutions Program

Thu, 28 Aug 2008 17:51:47 -0700

EMBARGO 8/20/08 10:30 AM PDT ============================ Continuent, Inc., a leading provider of commercial open source middleware solutions for database replication and scale-out, today announced it has been selected to join the Intel® Certified Solutions Program.

Continuent Launches Tungsten Database Scale-out Stack

Thu, 28 Aug 2008 17:51:47 -0700

Continuent Launches Tungsten Database Scale-out Stack. New Open Source Project Uses Multiple Copies of Data to Scale-out Database Solutions for High Availability and Performance Boost.

Bug 452431 – Can we have pgsql support in Postfix by default?

Tue, 19 Aug 2008 19:57:38 -0700

Announcement: The Pythian Group and Open Query: Partners

Tue, 19 Aug 2008 14:49:10 -0700

I’d like to share some great news — The Pythian Group and Open Query have become partners!

Open Query is a leading provider of high-quality MySQL, PostgreSQL and related training in Australia and New Zealand. They offer consulting services too, and are also known for their MySQL Graph Storage Engine. Feel free to browse through Open Query web-site for more info.

Open Query was founded by Arjen Lentz, who was employee number 25 at MySQL AB. If you follow the MySQL community then I’m sure you already read Arjen’s blog.

Since you’re reading this blog, I guess you probably already know what Pythian does, but if you want to learn more, please click through to our home page.

Together with Open Query, we are going to extend our service offerings and strengthen our positions in outsourced database management services, consulting, and training.

Index of /Linux/centos/5.2/centosplus/i386/RPMS

Tue, 19 Aug 2008 05:43:15 -0700

postfix-2.3.3-2.el5.centos.mysql_pgsql.i386.rpm postfix-pflogsumm-2.3.3-2.el5.centos.mysql_pgsql.i386.rpm

XML Support - PostgreSQL Wiki

Mon, 18 Aug 2008 23:43:00 -0700

Joshua Drake: PostgreSQL Conference: West. October 10th-12th Call for papers

Mon, 18 Aug 2008 22:05:28 -0700

The second annual PostgreSQL Conference: West is being held on October 10th through October 12th 2008 in the The Native American Student & Community Center at Portland State University.