Re: Slony RPM issue

Hi,

On Wed, 5 Oct 2005, Philip Yarra wrote:

> Hi Devrim, I ran into another RPM issue, this time with Slony.

:-)

> I grabbed the RPM from
> http://developer.postgresql.org/~devrim/slony/1.1.0/rpms/PG8.0.3/
>
> Trying to run slon_start, I got errors such as:
> $ slon_start --config /etc/slon_tools.conf 2
> Invoke slon for node 2 - @@@/slon -s 1000 -d2 -g 80 replication 'host=dev2
> dbname=booktown user=postgres port=5432' 2>&1
>> /var/log/slony/slony1/node2/booktown-2005-10-05_16:23:53.log &
> sh: line 1: @@@/slon: No such file or directory
> Slon failed to start for cluster replication, node node2
>
> This turned out to be because /usr/lib/pgsql/slon-tools.pm contained several
> un-expanded @@PGBINDIR@@ prefixes - once I replaced them with /usr/bin it all
> ran just fine.

Hrrm.

It seems that I've installed wrong file in the spec :( However slon-tools
file is not updated by the Makefile, so I'll try to fix that, too.

Thanks for the report. It will fixed in CVS and all the RPM sets later
today. Always feel free to send me a patch if you want, I can apply your
patch, too.

BTW, could you please report the possible Slony problems to
slony1-general(at)gborg(dot)postgresql(dot)org later?

Regards,
--
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-hackers-owner(at)postgresql(dot)org Wed Oct 5 11:57:21 2005
X-Original-To: pgsql-hackers-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 69695DA215
for <pgsql-hackers-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>; Wed, 5 Oct 2005 11:55:24 -0300 (ADT)
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 83238-10
for <pgsql-hackers-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>;
Wed, 5 Oct 2005 14:55:19 +0000 (GMT)
Received: from presinet.com (presinet.com [209.53.156.1])
by svr1.postgresql.org (Postfix) with ESMTP id AC8B2DA20D
for <pgsql-hackers(at)postgresql(dot)org>; Wed, 5 Oct 2005 11:55:20 -0300 (ADT)
Received: from [10.10.1.151] ([10.10.1.151]) by presinet.com with Microsoft SMTPSVC(6.0.3790.1830);
Wed, 5 Oct 2005 07:53:51 -0700
Message-ID: <4343E95D(dot)5000007(at)PresiNET(dot)com>
Date: Wed, 05 Oct 2005 07:55:25 -0700
From: Bricklen Anderson <BAnderson(at)PresiNET(dot)com>
User-Agent: Debian Thunderbird 1.0.6 (X11/20050802)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: prefix btree implementation
References: <Pine(dot)LNX(dot)4(dot)58(dot)0510042359110(dot)15377(at)eon(dot)cs>
In-Reply-To: <Pine(dot)LNX(dot)4(dot)58(dot)0510042359110(dot)15377(at)eon(dot)cs>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Oct 2005 14:53:51.0453 (UTC) FILETIME=[996588D0:01C5C9BC]
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.009 required=5 tests=[AWL=0.009]
X-Spam-Level:
X-Archive-Number: 200510/218
X-Sequence-Number: 74077

Qingqing Zhou wrote:
> I am not sure if this idea was mentioned before.
>
> The basic prefix btree idea is quite straightforward, i.e., try to
> compress the key items within a data page by sharing the common prefix.
> Thus the fanout of the page is increased and the benefits is obvious
> theorectically.
>
<snip>
>
> So together, there are basically four types of possible sharing:
> column-wise (case 1), character-wise (case 2), column-character-wise (case
> 3), and byte-wise (case 4).
>
Oracle implements something similar called index compression, but I believe it
is only for common column values. I haven't checked in versions>9r1 so maybe
there are other options implemented by now.

Jonathan Lewis describes some pros and cons here:
http://www.jlcomp.demon.co.uk/faq/compress_ind.html

--
_______________________________

This e-mail may be privileged and/or confidential, and the sender does
not waive any related rights and obligations. Any distribution, use or
copying of this e-mail or the information it contains by other than an
intended recipient is unauthorized. If you received this e-mail in
error, please advise me (by return e-mail or otherwise) immediately.
_______________________________