From: Shaun Thomas <sthomas@peak6.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: Jim Nasby <jim@nasby.net>
Cc: Anthony Presley <anthony@resolution.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Infinite Cache
Date: Tue, 5 Jul 2011 08:35:38 -0500
Message-ID: <4E13132A.9090204@peak6.com> (raw)
In-Reply-To: <CABUevEx=KcwZtCq7xchjuj8tM5UJ71movnDXp6X_2f1Z6vNJ4w@mail.gmail.com>
References: <BANLkTi=BWd5G_q2erCZK-Htd=CLU1n9R0Q@mail.gmail.com>
<6CEF0279-2FD6-4A55-B256-6DEDD124E799@nasby.net>
<CABUevEx=KcwZtCq7xchjuj8tM5UJ71movnDXp6X_2f1Z6vNJ4w@mail.gmail.com>
On 07/03/2011 06:21 AM, Magnus Hagander wrote:
> I was at one point told that *all* of infinite cache would be
> submitted to the community, but it was in need of some cleanup
> first.
I'm not sure what kind of cleanup would be involved, but we had some
problems with index corruption that wasn't fixed until a February patch
was applied. My guess is that earlier versions of Infinite Cache weren't
all that careful with verifying certain edge cases during connection
renegotiation or timeout scenarios. It only seemed to pop up once every
few billion queries, but that's all it takes to bring down a heavy OLTP
system.
I'd say it's probably safe enough these days. But it's also one of those
exclusive selling points they're using right now to garner EDB
customers. So I doubt it'll be released any time *soon*, though may make
it eventually.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
sthomas@peak6.com
______________________________________________
See http://www.peak6.com/email_disclaimer.php
for terms and conditions related to this email
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sthomas@peak6.com, magnus@hagander.net, jim@nasby.net, anthony@resolution.com
Subject: Re: Infinite Cache
In-Reply-To: <4E13132A.9090204@peak6.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox