[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: OpenLDAP with PostgreSQL backend, berkley just don't work for me.



Ok, never mind.... I should read the back-sql docs before
writting....... I'll have to keep fighting berkley. :-S

help. it is winning the battle :( .

I just don't know what else to do........


On 9/17/05, Jose Ildefonso Camargo Tolosa <ildefonso.camargo@gmail.com> wrote:
> Hi!
> 
> I'm about to do some tests with PostgreSQL backend, I just can't keep
> the berkley work find.  This is my DB_CONFIG , and it just keeps
> crashing, with very low load and a small directory:
> 
> set_cachesize 0 33554432 1
> set_lg_regionmax 262144
> set_lg_bsize 2097152
> #set_lg_dir /var/log/bdb
> #
> # Automatically remove log files that are no longer needed.
> set_flags DB_LOG_AUTOREMOVE
> # Just use these settings when doing slapadd...
> #set_flags DB_TXN_NOSYNC
> #set_flags DB_TXN_NOT_DURABLE
> 
> So, I decided to give a try to postgres backend, and I would like to
> hear any experiencies you may have with it.
> 
> I'm usign db-4.2.52, and openldap 2.2.28.  With very little load, at
> one moment the slapd just go to 99% processor use (it still works, but
> it happend), and then I just kill it (signal 9, signal 15 doesn't kill
> it) and run db4.2_recover and it starts working just fine for another
> day or so.  This far, I have not had any data loss, but it is annoying
> to see 100% CPU using all the day.
> 
> Thanks in advance,
> 
> Ildefonso Camargo.
>