投稿者: 管理者 投稿日時: 2012-2-3 17:00:00

Postgres Plus Solution Pack v9.1 がリリースされました。

PostgreSQL (includes StackBuilder) をインストール後、StackBuilder にて "Registration Required and Trial Products" を導入頂くことで Solution Pack をご利用頂けます。

PostgreSQL v9.1.2-1 は v9.0 では非同期のみだったレプリケーションに同期モードの追加や、トランザクションログ(WAL)を生成しない事で処理の高速化を行える新たな UNLOGGED TABLE テーブルタイプの追加等がなされております。

* Allow synchronous replication
* Add support for foreign tables
* Add per-column collation support
* Add extensions which simplify packaging of additions to PostgreSQL
* Add a true serializable isolation level
* Support unlogged tables using the UNLOGGED option in CREATE TABLE
* Allow data-modification commands (INSERT/UPDATE/DELETE) in WITH clauses
* Add nearest-neighbor (order-by-operator) searching to GiST indexes
* Add a SECURITY LABEL command and support for SELinux permissions control
* Update the PL/Python server-side language

ソフトウェアダウンロードからダウンロードが可能です。



投稿者: 管理者 投稿日時: 2011-5-27 9:00:00

!満員御礼!
数多くの皆様のご参加、誠に有難うございます。

本カンファレンスがメディアに取り上げられました。
サイオステクノロジー、OSSの総合イベント「オープンソースサミット開催」、レッドハットが協賛


投稿者: 管理者 投稿日時: 2011-4-12 11:43:30

pg_upgrade コマンドに不具合が発見されました。すでに pg_upgrade コマンドをご利用の場合には、下記の手順で修正を試みてください。まだ利用していない場合には、アップデートの適用をお願いします。




IS THIS FIX FOR ME?
====================
This Fix is for customers using:

pg_upgrade and (formerly) pg_migrator


FIX STATUS
====================
A bug has been discovered in all released versions of pg_upgrade and
(formerly) pg_migrator. Anyone who has used pg_upgrade or pg_migrator
should take the following corrective actions as soon as possible.
Youmight also want to make a backup of the pg_clog directory if you do
not already have a recent copy. If you fail to take action promptly, it
might result in unexpected downtime.

This bug can cause queries to return the following error:

ERROR: could not access status of transaction ######
DETAIL: could not open file "pg_clog/####": No such file or directory=20

This error prevents access to very wide values stored in the database.

To prevent such failures users need to run the following psql script, as
the superuser, in all upgraded databases as soon as possible:

-- This script fixes data in pre-8.4.8 and pre-PG 9.0.4
-- servers that were upgraded by pg_upgrade and pg_migrator.
-- Run the script using psql for every database in the cluster
-- except 'template0', e.g.:
-- psql -U postgres -a -f pg_upgrade_fix.sql dbname
-- This must be run from a writable directory.
--
-- Depending on the size and configuration of your database,
-- this script might generate a lot of I/O and degrade database
-- performance. Users should execute this script during a low
-- traffic period and monitor the database load.

CREATE TEMPORARY TABLE pg_upgrade_fix AS
SELECT 'VACUUM FREEZE pg_toast.' || c.relname || ';'
FROM pg_class c, pg_namespace n
WHERE c.relnamespace = n.oid AND
n.nspname = 'pg_toast' AND
c.relkind = 't'
ORDER by c.oid;
\copy pg_upgrade_fix TO 'pg_upgrade_tmp.sql';
\i pg_upgrade_tmp.sql

A fix will be included in upcoming Postgres releases 8.4.8 and 9.0.4.
These releases will remove the need to run the above script after
upgrades by correctly restoring all TOAST tables in the migrated
databases. However, databases which have already been upgraded stillneed
the script run, even if they are running Postgres 9.0.4.



« 1 (2) 3 4 5 6 »
ログイン
ユーザー名:

パスワード:



パスワード要求 | 新規登録

検索
メインメニュー
 


Copyright(C) SIOS Technology, Inc. All Rights Reserved