[2021 total ]
Josh Berkus: The Three Database Clustering Users

The PostgreSQL community and the database industry have a bewildering profusion of clustering product and projects, utilizing a plethora of technologies and optimized for a diversity of different requirements. Clusters are single-master ... [More] , multi-master, middleware, database engine, application-based, statement-based, group communication, distributed table, partitioned database, federated, shared disk, shared memory, shared nothing, highly available, load balanced, and/or eventually consistent. [Less]

Selena Deckelmann: Cluster Developer Meeting recap



UPDATE: See bottom of post.

We held a PostgreSQL cluster developer meeting on Thursday, November 19, 2009 in Tokyo. About 25 people were in attendance, and seven projects presented status updates. Projects represented included ... [More] pgCluster, PostgresForest, Postgres-R, Streaming Replication (slated to be included in core for version 8.5), Postgres-2 (not quite available), GridSQL, the Skype Skytools team (Londiste), Bucardo and Slony. Details of our discussions are being documented on the PostgreSQL wiki, and we’ve started a new mailing list.

The group of developers came up with a list of features that they would appreciate being implemented in Postgres soon, and we will be filling out the details in the coming weeks.

Our first milestone as a group is to create a detailed matrix of features to help users more easily navigate between the different solutions. I’m also going to arrange for a documentation sprint, dedicated to creating introductory documentation for new database administrators interested in clustering technology for Postgres. I’ll report out in December about how this work is going!

Josh has also posted a summary of the cluster meeting, and our next actions. [Less]

Josh Berkus: Collaborating on Clustering

For the last several years, PostgreSQL has suffered from having numerous, incomplete, unpolished, and poorly-publicized clustering and replication tools. It's time to fix that.

Andrew Dunstan: Oh, the irony

H/T Crad for this one

Joshua D. Drake: PDXDjango roundup: I finally got my Martini

Shout out to Mark Long and Lacey Powers for showing up to support a Pg dude in a foreign land. Preceding my talk on PostgreSQL Performance, Adam Lowry gave and interesting intro to a database connection pooling module he wrote for Django. Essentially ... [More] they bolted SQLAlchemy's pooler into Django. He then gave some metrics, showing that through the connection pooler they dropped overall request time in half. It was a basic and good indicator of why connection pooling is good, even on smaller applications. [Less]

US PostgreSQL Association: PgUS Community Member Update 11/09:

JD wrote:

So what is going on and what has happened over the last year?

First and foremost, I should mention that PgUS is about to have an election for 3 board seats. The current nominees are:

Michael Brewer
Joshua ... [More] Drake
Kevin Kempter
Bruce Momjian
Greg Smith

You need to be a Professional or Student Member to vote. In order to update your membership to a voting membership open your favorite web browser and go to:

https://www.postgresql.us/join

read more [Less]

Joshua D. Drake: Speaking at PDXDjango Tonight on PostgreSQL Performance

I have the unexpected pleasure of speaking at PDXDjango tonight on PostgreSQL performance. Their meetings are 90 minutes with about 60 minutes (in theory) for the main speaker. The talk I am giving is a quick introduction to PostgreSQL Performance. ... [More] The description I gave to the group was: I am a Django developer not a DBA.
I know nothing about PostgreSQL performance.
What 10 things (it will be more) can I change to make PostgreSQL faster?
I am being as thorough as possible based on the time constraints and explaining what each option is and how it works. I didn't want to just say, "Change it to 10".

If you are in the neighborhood, stop by and let me know all the things I say that are wrong. The meeting starts at 7:00PM.

PIE
1227 NW Davis St
Portland, Oregon
(At the corner of NW Davis & NW 12th). [Less]

Francisco Figueiredo Jr: Npgsql 2.0.7 released!

Hi all,

Npgsql 2.0.7 is out. This is a minor bug fix release.

The most notorious bug fix is one made by Josh Cooley about possible freezes and strange exceptions when canceling a query. So, if you were having any problem like this ... [More] , please give it a try.

Download it from: downloads.npgsql.org

This is the release notes of this release:

Bugs fixed:

[#1010527] Fix query timeout connection corruption.

[#1010700] Capture parameter names with NpgsqlCommandBuilder.DeriveParameters. Thanks Brian Schloz (bschloz @nospam@ hotmail.com) for patch. Also added nunit testcase.

[#1010668] Npgsql ConnectionStringBuilder provides no connectionstring properties. Now Npgsql correctly reports default connectionstring properties. Thanks Alaric Dailey for heads up and patch!

Fixed bug when trying to retrieve a date value with -infinity value. See more here: http://pgfoundry.org/forum/message.php?msg_id=1005249 Thanks Andrus Moor for bug report and test case and Laurenz Albe for reporting the commit where the infinity date value was added.

[#1010679] NpgsqlCommand.GetClearCommandText speed optimization. Thanks Dmitri Maximov (dmitri.maximov @nospam@ dataobjects.net) for patch.

Thanks all for your help and feedback with this release! [Less]

Hubert Lubaczewski: Waiting for 8.5 – TRIGGERS on columns

On 14th of October Tome Lane committed new patch from Itagaki Tahahiro:
Log Message:
-----------
Support SQL-compliant triggers on columns, ie fire only if certain columns
are named in the UPDATE's SET list.
 
Note: the ... [More] schema of pg_trigger has not actually changed; we've just started
to use a column that was there all along. catversion bumped anyway so that
this commit [...] [Less]

Hubert Lubaczewski: Waiting for 8.5 – Named function arguments

Pavel Stehule – hero for everybody writing stored procedures, wrote, and later Tom Lane committed patch which adds named arguments for functions:
Log Message:
-----------
Support use of function argument names to identify which ... [More] actual arguments
match which function parameters. The syntax uses AS, for example
funcname(value AS arg1, anothervalue AS arg2)
 
Pavel Stehule

So, let’s see how it works.
CREATE OR [...] [Less]