On Wed, Sep 04, 2013 at 09:41:15AM +0200, Silvio Moioli wrote:
We recently stumbled in some failing tests downstream and we were
wondering why it was chosen to use pltcl in the new logging schema
I've decided it was the optimal solution for the task. Faster than
temporary tables, less invasive
On 09/11/2013 08:28 AM, Jan Pazdziora wrote:
On Wed, Sep 04, 2013 at 09:41:15AM +0200, Silvio Moioli wrote:
We recently stumbled in some failing tests downstream and we were
wondering why it was chosen to use pltcl in the new logging schema
I've decided it was the optimal solution for the
On 09/11/2013 02:28 PM, Jan Pazdziora wrote:
Which for typical web application request handling is what you want,
isn't it? The whole request processing is one transaction and
releasing it gives you nice cleanup.
It is, except for a very few cases of commit-in-the-middle.
Does it happen in
- Original Message -
On 09/11/2013 02:28 PM, Jan Pazdziora wrote:
Which for typical web application request handling is what you want,
isn't it? The whole request processing is one transaction and
releasing it gives you nice cleanup.
It is, except for a very few cases of
There is an issue with the default yum repo label with some of the new
repositories, particularly the Scientific Linux and Oracle Linux Spacewalk
Server/Client repos. The full text expands to greater than 64 chars, which is
the limit of the database field that stores the repository name. If you
Spacewalk already had the Oracle Linux 4 and 5 GPG keys. This adds the GPG key
used to sign Oracle Linux 6 packages.
---
schema/spacewalk/common/data/rhnPackageKey.sql |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/schema/spacewalk/common/data/rhnPackageKey.sql
On Wed, Sep 11, 2013 at 11:20:15AM -0400, Stephen Herr wrote:
Normally the case yes, but there are at least a couple of instances
where we commit a single request as multiple transactions to avoid
overrunning Oracle's rollback buffer. One example that jumps to mind
is generating yum repodata
Hi,
Please ignore this patch. There are other changes required to support the
Oracle Linux 6 key, which I'm still researching. Apologies for the noise.
Thanks,
Avi
On 12/09/2013, at 8:46 AM, Avi Miller avi.mil...@oracle.com wrote:
Spacewalk already had the Oracle Linux 4 and 5 GPG keys. This
Make sure you check latest code - I submitted a number of changes in the last
day or so to address *exactly* the need to reset for logging after a commit
in the testcases. I'm sure there are still a few places, but it's better
now...
Thanks! I noticed your latest patches while developing