That's where we're having difficulty. Our requirements are that the
data must be strongly protected, but the appropriate people must be
able to do (often complex) searches on it that complete in record
time.
an index on the encrypted SSN field would do this just fine. if
authorized
Hi,
I'm setting up a replacement standby server. I've had this working
before until the old standby server lost a drive array and a
motherboard. So, my process was working. On the other hand, the old
slave was debian etch, with a backported 8.2 release, and the new one
is ubuntu 8.04.
2) What file is not found? It sorta looks like the pg_standby
binary, but I'm not sure that I believe that.
Permissions problems on some containing directory, perhaps?
It's the same directory as the postgresql binaries, and they all have
sane
permissions. (root:root, 755). Ls finds it,
MySQL is CLEARLY SUPERIOR in terms of
- usability
- see above
- performance
- uses index for for min()/max()
- reliability
- no need to use vacuum
- no need to dump and restore databases for version upgrade
- never screwed up any of my databases
You forgot space saving storage of
On Dec 3, 2003, at 1:05 PM, Vivek Khera wrote:
CM == Carlos Moreno [EMAIL PROTECTED] writes:
CM What would be your advice? Is 7.3.4 the recommended one
CM if we need reliability? Or has 7.4 earned sufficient
CM trust by now?
CM Also, how about back compatibility? Should I expect some
CM
Slightly off topic confirmations...
And here are are the default settings for OS X 10.2.6:
sysctl -w kern.sysv.shmmax=4194304
Seems to be the default on 10.2.8 as well.
10.1.5 doesn't seem to have a kern.sysv.* section:
[broccoli:~] erics% sysctl kern.sysv.shmmax
second level name sysv in
