Re: Oracle 10g Express - any danger for Postgres?

From: Devrim GUNDUZ <devrim(at)gunduz(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: nikolay(at)samokhvalov(dot)com, Postgresql-General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Oracle 10g Express - any danger for Postgres?
Date: 2005-10-30 19:37:01
Message-ID: Pine.LNX.4.63.0510302136280.8242@mail.kivi.com.tr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Hi,

On Sun, 30 Oct 2005, Bruce Momjian wrote:

>> 'Oracle intends to release a free version of its database, a reaction
>> to the growing competitive pressure from low-end open-source
>> databases.'
>>
>> Your thoughts?
>
> It probably has little impact on us. It is useful perhaps for developer
> servers at existing Oracle sites.

I hope one day Oracle will understand that "Free Software is not Free
Beer".

--
Devrim GUNDUZ
Kivi Bilişim Teknolojileri - http://www.kivi.com.tr
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org
>From pgsql-general-owner(at)postgresql(dot)org Sun Oct 30 15:42:50 2005
X-Original-To: pgsql-general-postgresql(dot)org(at)localhost(dot)postgresql(dot)org
Received: from localhost (av.hub.org [200.46.204.144])
by svr1.postgresql.org (Postfix) with ESMTP id B7EE2DB3F9
for <pgsql-general-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>; Sun, 30 Oct 2005 15:42:49 -0400 (AST)
Received: from svr1.postgresql.org ([200.46.204.71])
by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
with ESMTP id 24500-09
for <pgsql-general-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>;
Sun, 30 Oct 2005 19:42:47 +0000 (GMT)
Received: from mercury.wardbrook.com (host-84-9-98-118.bulldogdsl.com [84.9.98.118])
by svr1.postgresql.org (Postfix) with ESMTP id C5F9BDB3C5
for <pgsql-general(at)postgresql(dot)org>; Sun, 30 Oct 2005 15:42:47 -0400 (AST)
Received: from localhost (localhost.localdomain [127.0.0.1])
by mercury.wardbrook.com (Postfix) with ESMTP
id 5BA78532EB; Sun, 30 Oct 2005 19:39:54 +0000 (GMT)
Received: by mercury.wardbrook.com (Postfix, from userid 505)
id 277F1532F6; Sun, 30 Oct 2005 19:39:53 +0000 (GMT)
Received: from [192.168.0.64] (unknown [192.168.0.1])
by mercury.wardbrook.com (Postfix) with ESMTP
id E9EF8532EB; Sun, 30 Oct 2005 19:39:51 +0000 (GMT)
Message-ID: <4365237B(dot)5070006(at)wardbrook(dot)com>
Date: Sun, 30 Oct 2005 19:48:11 +0000
From: John Sidney-Woollett <johnsw(at)wardbrook(dot)com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Please HELP - URGENT - transaction wraparound error
References: <4364894A(dot)5000209(at)wardbrook(dot)com> <20051030135627(dot)GA19496(at)svana(dot)org> <4364DC5A(dot)8050900(at)wardbrook(dot)com> <823(dot)1130688328(at)sss(dot)pgh(dot)pa(dot)us> <4364F3A8(dot)7060906(at)wardbrook(dot)com> <7690(dot)1130690087(at)sss(dot)pgh(dot)pa(dot)us> <4364FA20(dot)4000502(at)wardbrook(dot)com> <12531(dot)1130694892(at)sss(dot)pgh(dot)pa(dot)us> <436513E9(dot)7050503(at)wardbrook(dot)com> <14516(dot)1130699874(at)sss(dot)pgh(dot)pa(dot)us>
In-Reply-To: <14516(dot)1130699874(at)sss(dot)pgh(dot)pa(dot)us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.1 required=5 tests=[AWL=0.100]
X-Spam-Score: 0.1
X-Spam-Level:
X-Archive-Number: 200510/1843
X-Sequence-Number: 86071

"Panic" - that's my middle name. ;)

Had I known how to identify the database at fault, and that it would
have had no effect on the other databases, then I would have handled
this episode differently.

In the event, things seem to be OK. Our old slave db is now acting as
master and the old master rebuilt as the new slave ... courtesy of slon.

I'd like to move to 8.1 but I'm waiting for a quiet period when there's
less development/fire fighting so that I can test all the java
components of our webapp and then manage the upgrade properly.

Maybe suppressing other vacuums once a month, and running the "vacuumdb
-a" option instead wouldn't be a bad idea...

Many thanks for all your support and advice - you've been great help
(and comfort).

John

Tom Lane wrote:
> John Sidney-Woollett <johnsw(at)wardbrook(dot)com> writes:
>
>>Just out of curiousity would the wraparound error (for mail_lxtreme)
>>actually have affected data in bp_live?
>>Could I just have deleted mail_lxtreme and then continued to use bp_live
>>as though nothing had happened?
>
>
> No, and yes, which is why panicking was not warranted ;-)
>
> Martijn's advice to be using "vacuumdb -a" every so often is well given,
> though.
>
> You could also consider switching over to autovacuum, particularly as of
> 8.1. (I'm not sure how much I trust the contrib version that exists in
> 8.0, and 7.4's is definitely pretty buggy, but I believe 8.1's can be
> relied on to prevent this sort of thing.)
>
> regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Magnus Hagander 2005-10-30 20:40:21 Re: Why database is corrupted after re-booting
Previous Message John Sidney-Woollett 2005-10-30 19:34:12 Re: Please HELP - URGENT - transaction wraparound error