| From: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
|---|---|
| To: | Mathieu Arnold <mat(at)mat(dot)cc> |
| Cc: | "Chad R(dot) Larson" <clarson(at)eldocomp(dot)com>, LN Cisneros <chulat(at)mail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: removal from list |
| Date: | 2003-03-14 02:17:03 |
| Message-ID: | 20030313221637.U4545@hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Thu, 13 Mar 2003, Mathieu Arnold wrote:
>
>
> --Le 13/03/2003 15:16 -0400, Marc G. Fournier écrivait :
>
> > On Thu, 13 Mar 2003, Chad R. Larson wrote:
> >
> >> At 12:15 PM 3/13/2003 -0400, Marc G. Fournier wrote:
> >> > the database (Berkeley DB is used) backend for the majordomo2 lists
> >> > isn't the most stable, so we've been having periodic corruption
> >> > problems where we have to rebuild it
> >>
> >> Does anyone else see the irony here?
> >>
> >> How about using, oh say, PostgreSQL for the database? :-)
> >
> > Do you volunteer to dive into the Majordomo2 code and extend it to use
> > PgSQL? i started, but time didn't allow me to get very far with it, but
> > if you have the time and wish to do so, I have commit access to the
> > repository to get the changes in place ...
>
> Did you have a look at what I committed to Mj::SimpleDB::SQL ?
> I still have a few things to work out, and if you don't use sublists, you
> can dive in, it works :)
You feel confident enough for me to use it on these lists? :)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-03-14 02:43:57 | Re: Password authentication |
| Previous Message | Partho Bhowmick | 2003-03-14 01:27:54 | Regular expressions in PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-03-14 04:10:22 | Re: now() AT TIME ZONE interval '-5 hours' returns type interval??? |
| Previous Message | Joshua Moore-Oliva | 2003-03-14 01:45:53 | Re: now() AT TIME ZONE interval '-5 hours' returns type interval??? -- more info, looks like a postgres bug |