Re: 8.1 Release Candidate 1 Bundled ...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Lamar,

On Mon, 31 Oct 2005, Lamar Owen wrote:

>> So thinking that:
>
>> * Beta and RC RPMs are used only by testers
>> * We use the beta and RC steps to build the new RPM sets, so that means
>> that actually they are not production quality looking from the RPM
>> perspective.
>
> By way of clarification, as I am the one who wrote that portion of the
> spec file, an 'RPM prerelease' and a 'beta' weren't intended to be the
> same thing; the line in the spec referenced was for my own use to remind
> me that my own internal testing packages (with a release number 0.x)
> weren't intended for public consumption. Devrim, you can remove that
> section of the spec file at any time at this point, because you are using
> CVS for the purpose that I was using 'prerelease' RPMs.

Ok, I've removed that part from the spec files.

> Historically, beta and release candidate RPM's were put on the main ftp
> site but flagged as beta quality. I certainly appreciate your dilligence
> in following those instructions I wrote long ago, but, thanks to your
> smoother release process (in no small part due to the use of CVS) those
> instructions are obsolete. Many thanks for being that dilligent!

:) Ok, I will be putting the beta and RC RPMs to FTP site from now on.

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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDZ9Is4zE8DGqpiZARAku+AJ90HZHQNUeLQ+a7zy7ge2hFvNpLegCgqD0U
2yf2pDfmsSGrZZDBWBf7yZU=
=Wxyt
-----END PGP SIGNATURE-----
>From pgsql-hackers-owner(at)postgresql(dot)org Tue Nov 1 16:48:47 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 4A6FBDB6D3
for <pgsql-hackers-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>; Tue, 1 Nov 2005 16:48:46 -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 15212-07
for <pgsql-hackers-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>;
Tue, 1 Nov 2005 20:48:43 +0000 (GMT)
Received: from mx1.surnet.cl (mx1.surnet.cl [216.155.73.180])
by svr1.postgresql.org (Postfix) with ESMTP id 2C83BDB6CA
for <pgsql-hackers(at)postgresql(dot)org>; Tue, 1 Nov 2005 16:48:43 -0400 (AST)
Received: from unknown (HELO cluster.surnet.cl) ([216.155.73.165])
by mx1.surnet.cl with ESMTP; 01 Nov 2005 17:50:39 -0300
X-IronPort-AV: i="3.97,276,1125892800";
d="scan'208"; a="21448617:sNHT33648240"
Received: from alvh.no-ip.org (200.85.218.142) by cluster.surnet.cl (7.0.043) (authenticated as alvherre(at)surnet(dot)cl)
id 4350159700225AD6; Tue, 1 Nov 2005 17:48:45 -0300
Received: by alvh.no-ip.org (Postfix, from userid 1000)
id 0EE9DC2D450; Tue, 1 Nov 2005 17:49:49 -0300 (CLST)
Date: Tue, 1 Nov 2005 17:49:48 -0300
From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: slru.c race condition
Message-ID: <20051101204948(dot)GC21459(at)surnet(dot)cl>
Mail-Followup-To: Chris Browne <cbbrowne(at)acm(dot)org>,
pgsql-hackers(at)postgresql(dot)org
References: <D1D2D51E3BE3FC4E98598248901F759402C88F12(at)ausmail2k4(dot)aus(dot)pervasive(dot)com> <15543(dot)1130714273(at)sss(dot)pgh(dot)pa(dot)us> <20051031234731(dot)GQ20349(at)pervasive(dot)com> <20051101000259(dot)GE12906(at)surnet(dot)cl> <20051101005604(dot)GU20349(at)pervasive(dot)com> <21073(dot)1130814779(at)sss(dot)pgh(dot)pa(dot)us> <20051101142355(dot)GB17904(at)surnet(dot)cl> <20051101184944(dot)GD20349(at)pervasive(dot)com> <603bmg9mvb(dot)fsf(at)dba2(dot)int(dot)libertyrms(dot)com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <603bmg9mvb(dot)fsf(at)dba2(dot)int(dot)libertyrms(dot)com>
User-Agent: Mutt/1.5.10i
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=1.666 required=5 tests=[AWL=-0.253,
DNS_FROM_RFC_ABUSE=0.479, DNS_FROM_RFC_POST=1.44]
X-Spam-Score: 1.666
X-Spam-Level: *
X-Archive-Number: 200511/31
X-Sequence-Number: 75313

Chris Browne wrote:
> jnasby(at)pervasive(dot)com ("Jim C. Nasby") writes:
>
> > On Tue, Nov 01, 2005 at 11:23:55AM -0300, Alvaro Herrera wrote:
> >> Tom Lane wrote:
> >> > "Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> >> > > AFAIK they're not using subtransactions at all, but I'll check.
> >> >
> >> > Well, yeah, they are ... else you'd never have seen this failure.
> >>
> >> Maybe it's in plpgsql EXCEPTION clauses.
> >
> > Err, I forgot they're using Slony, which is probably using savepoints
> > and/or exceptions.
>
> Slony-I does use exceptions in pretty conventional ways; it does *not*
> make any use of subtransactions, because it needs to run on PG 7.3 and
> 7.4 that do not support subtransactions.

Hmm, does it use the BEGIN/EXCEPTION/END construct at all? Because if
it does, it won't work on 7.4; and if it doesn't, then it isn't using
savepoints in 8.0 either.

--
Alvaro Herrera http://www.amazon.com/gp/registry/5ZYLFMCVHXC
"Siempre hay que alimentar a los dioses, aunque la tierra esté seca" (Orual)