We (in MicroOLAP Technologies) just finished client libraries update for 8.4.1 version.

Quick facts:

• Two packages were updated:
• Deployment libraries shipped with PostgreSQL installation
• Deployment libraries built with MinGW environment
• Both packages are built against 8.4.1 version of PostgreSQL
• Comparing to 8.3.6 version libpq.dll library shipped with PostgreSQL installation depends on 12 libraries now (were 9 in 8.3.6)
• Dump and restore libraries for 8.3.x and 8.2.x PostgreSQL branches are included into “Deployment libraries built with MinGW environment” package
• Included dump libraries (pg_dump-8.2.14.dll, pg_dump-8.3.8.dll) may be used with PaGoDump utility either

Enjoy!

David Fetter wrote a post about GCD calculations using SQL.

Reading this post I remembered my university years and course of number theory in particular. It’s still impossible to forget Mrs. Alexeeva’s lectures. Who knows her will understand what I mean.

Anyway. In my previous post I proposed function for GCD calculation. Thus we can calculate LCM either. The only thing we should recall that

LCM(a,b) · GCD(a,b) = |a · b|
=>
LCM(a,b) = |a · b| ÷ GCD(a,b)

However, I suggest you to change formula a bit to

LCM(a,b) = |a| ÷ GCD(a,b) · |b|

This is the correct change because GCD is the divisor for both numbers. This will reduce the required storage needed for intermediate result.

CREATE OR REPLACE FUNCTION lcm(bigint, bigint)
  RETURNS bigint AS
$BODY$
  SELECT $1 / gcd($1, $2) * $2;
$BODY$
IMMUTABLE
STRICT
LANGUAGE SQL;

PS. gcd(bigint, bigint) function declaration was in my previous post.

Continuing the idea outlined earlier I would like to offer my version of the GCD function.

CREATE OR REPLACE FUNCTION gcd(bigint, bigint) RETURNS bigint AS
$BODY$
 WITH RECURSIVE t(a, b) AS (
	VALUES (abs($1) :: bigint, abs($2) :: bigint)
UNION ALL
	SELECT b, mod(a,b) FROM t
	WHERE b > 0
)
SELECT a AS gcd FROM t WHERE b = 0;
$BODY$
IMMUTABLE
STRICT
LANGUAGE SQL;

BTW, I believe this version should be available in the PostgreSQL Wiki instead of David Fetter’s one (David, with all respect! It was inspired by yours.).

“Why?” — you may ask.

• It is much, much faster;
• It handles negative numbers properly;
• Because I wish to make this world better!

Cheers! Don’t do drugs!

David Fetter wrote a post about how to find GCD of two numbers. In his post David call it “a quick way”. But let me disagree. This is more efficient way:

WITH RECURSIVE t(a, b) AS (
	VALUES (38, 12)
UNION ALL
	SELECT b, mod(a,b) FROM t
	WHERE b > 0
)
SELECT a AS gcd FROM t WHERE b = 0;

Cheers!

As recently promised I will shortly disclose the milestones of PgMDD upcoming release.

First of all, PgMDD will have a new look. I have already mentioned about this.

Extended SQL Editor

But let’s talk about functionality. New release will provide extended SQL Editor with code completion and syntax validation. I hope this might make life better. Now all edits which may hold SQL statements will have ability to open extended SQL Editor, e.g. column DEFAULT value, expression of CHECK constraint, WHERE clause for table rule etc.

It may help you quickly insert tables and functions, columns and parameters, standard PostgreSQL functions and datatypes into SQL script.

ACL Manager

Also new release will support objects privileges, thus to change them you may use ACL Manager aka Grant Manager.

Due to privileges support new privileges options appear in Database Generation dialogue window as well as options for object’s owner.

And the Database Modification dialogue get “Override grant privileges” option either.

For customization fanatics we prepared special surprise. To see it check Display Preferences dialogue.

Among others improvements I would like to highlight the following:

• support for VARIADIC parameters;
• support for window functions;
• support for database’s LC_COLLATE and LC_CTYPE options.

PS There several bugs were fixed too. But who cares…

As you probably know the latest PaGoDump 8.4.1 version allows library selection.

Here is the tiny video tutorial (~240Kb) about this feature.

Today MicroOLAP team made the beta of upcoming Database Designer for PostgreSQL v1.9.3 release available.

Stay tuned for details.

New PaGoDump is available! At last. We faced with a lot of mystical barriers during this release. It supposed to be public a week ago. Whatever…

New release will provide a brand new functionality — custom library selection!

Now two libraries will be available: 8.3.8 and 8.4.1, but this is only the beginning — 8.2.x branch will be included in the very next release.

P.S. Kishkin, where you got to?

Tom,
on behalf of MicroOLAP team I wish you luck!

Many of us wish you to be healthy. But here in Ukraine people say: “Porker was a healthy one, but it was no good for him.” That’s why we wish you only luck!

Congratulations!

PS Today is “Jewish New Year” (ראש השנה‎) celebrated. Shana Tova (שנה טובה)!

PPS Yeah, I know the pretty same message appeared on pgsql-hackers@postgresql.org earlier… Who cares!

PostgreSQL started the v8.4.1 race and PostgresDAC takes the baton – new release with 8.4.1 support is already available.

Alongside with orphanhood solution now you may manually choose what library should be used by TPSQLDump and TPSQLRestore.

For those who stuck in the past, dump and restore libraries for 8.3.x server branch available either.

Take care!

P.S.: Yeah, btw – “Baton” in Russian means “long loaf”. Holy true! Go Google it!