Howard Chu authored 10 years ago and Quanah Gibson-Mount committed 10 years ago

rename ppolicy_close -> ppolicy_db_close for consistency

Howard Chu authored 10 years ago and Quanah Gibson-Mount committed 10 years ago

don't free pwcons unless we're actually destroying this DB

Howard Chu authored 10 years ago and Quanah Gibson-Mount committed 10 years ago

Go directly to local backend when fetching local entry

Howard Chu authored 10 years ago and Quanah Gibson-Mount committed 10 years ago

In server mode, make sure the entry was actually ours

Howard Chu authored 10 years ago and Quanah Gibson-Mount committed 10 years ago

They were obsoleted by ITS#6737 and have been redundant ever since.
(commit 15f1e7bd)

FIRST_DUP/LAST_DUP should succeed even on non-duplicate values
PREV_DUP should reset cursor's EOF flag.

Add olcSssVlvMaxPerConn to the olcSssVlvConfig objectClass

MIPS chips require manual control of on-chip caches. The cacheflush
syscall being used here only exists on MIPS Linux, other OSs will
require revisiting.

Howard Chu authored 10 years ago and Quanah Gibson-Mount committed 10 years ago

It can still run after ppolicy_close has freed the connection table

return MDB_NOTFOUND if the cursor is empty

Always write mapsize = max(other metapage:mapsize, env:mapsize).

Revert "ITS#7789 Fix resize vs MDB_NOMETASYNC, and a comment."
Revert "ITS#7789 more"
Revert "Revert "ITS#7789 update RESIZED errmsg text""
Revert "ITS#7789 update RESIZED errmsg text"
Revert "ITS#7789 persist mapsize changes"

This reverts commit 02285aca.
This reverts commit 38e71c68.
This reverts commit a5e4eecb.
This reverts commit d8e18551.
This reverts commit 5926e54b.

    Add sc_writewait callback

    Invoked before a blocked writer waits for socket to be writable.
    Use in back-mdb to release reader txn while waiting.

James M Leddy authored 13 years ago and Quanah Gibson-Mount committed 10 years ago

From RFC 2782:

  A client MUST attempt to contact the target host with the
  lowest-numbered priority it can reach.

This patch sorts the DNS SRV records by their priority, and
additionally gives records with a larger weight a higher probability
of appearing earlier. This way, the DNS SRV records are tried in the
order of their priority.