Marc Munro wrote:
For the record, here are the results of our (ongoing) inevstigation into
the index/heap corruption problems I reported a couple of weeks ago.
We were able to trigger the problem with kernels 2.6.16, 2.6.17 and
2.6.18.rc1, with 2.6.16 seeming to be the most flaky.
By
Joshua D. Drake wrote:
Bruce Momjian wrote:
Joshua D. Drake wrote:
I think we should drop the term usability as a selling part of the
PR and push it into further description.. Instead we should use a
slightly more expensive word (think 50 cents, not 5). :)
Fine, I am all ears. Also, a
Joshua D. Drake wrote:
I am interrested in finding out what you folks mean by usability and
refinement. How do you measure it? These seem to me to be
unmeasurable hackneyed terms with little intrinsic meaning!
Yep you are absolutely right. That is what press releases are all about.
So
Can you guys conceive of the thousands of hours of chat you guys are
racking upinstead of real hacking because you have an inadequate working
structure? This is by far the chattiest and least worthwhile listserv
in the bsd world. Bar none.
--
No virus found in this outgoing message.
Marc G. Fournier wrote:
On Fri, 11 Aug 2006, Alvaro Herrera wrote:
I am suggesting that. I have heard all the old discussions about not
using a bugtracker, but in all fairness, I think some of us have to
create critical mass and get something started.
I will install anything, and
Christopher Kings-Lynne wrote:
We have three candidates already -- debbugs, RT and Gnats. The first
has the advantage that was written by hackers, for hackers, so it
doesn't have any of the insane for end users stuff which annoys so
many people around here ;-) (On the other hand it does have
Jim C. Nasby wrote:
On Tue, Aug 15, 2006 at 10:43:12PM -0700, Josh Berkus wrote:
Tom,
These days I doubt there's anyone around the project who refuses to use
a web browser at all. However, I still personally find it much more
convenient to read and respond to mailing-list postings
One person who commented on the The business of Postbrsql made this comment:
Posted Aug 3, 2006 8:45 UTC (Thu) by subscriber *jgarzik* [Link
http://lwn.net/Articles/193946/]Cluster immaturity. MySQL has been
shipping a workable single-master replication+failover for quite a while
now in most
Bruce Momjian wrote:
Do we want to replace our /contrib/isbn with this, or have it pgfoundry?
---
Jeremy Kronuz wrote:
I worked on this ISBN/ISSN/ISMN/EAN13 module about more than a year
ago, and I was wondering if it
Jeremy Kronuz wrote:
I suppose having it to replace the current contrib/isbn would be a
good option, this 13 digits ISBN will be the standard by 2007, and
some publishers are already issuing 13 digit ISBN numbers since last year.
The module I created uses int64 instead of strings, for the
Jeremy Kronuz wrote:
Michael wrote:
I do hope that your algorithm for generating 13 digits from 10 has been
validated with isbn.org, since all the check digits will change. I
believe it is crucial for postgresql to generate isbn codes in both 10
and 13 digits
Indeed now that see the
11 matches
Mail list logo
