running pgsql 7.2.1 on redhat7.3 SMP. installed a hacked glibc to fix the
mktime() timezone problem for dates < 1970
(http://rpms.arvin.dk/glibc/rh73/i686/)
three times now the backend process has unexpectedly quit. what happens is
the postmaster process and the stats processes disappear and only
hecked out the cwd in /proc, it is /var/lib/pgsql (actally i symlinked it
into another fs) which is postgres:postgres mode 700.
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Tim Lynch" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent:
operationally, disk subsystems trump software raid for primary dataset
storage:
battery backed cache - safety first.
portability - plug it into any other host, or more than one host on the scsi
bus (fc-al loop).
raid on a pci card or raid on the motherboard need not apply less they sport
battery a
First, sorry for the OT, flame me off-list!
I'm a sysadmin being impressed into dba service. i've been getting along
pretty well writing queries and making reports, but i've got some questions.
suggestions for a good list/forum for help?
from two tables both with email_addr columns, i want a dist
UNION! thanks everyone!
i'll take this stuff up on the pgsql-sql list in the future.
union does intra- and inter- table distinct, notice `red' and `two':
test=> select str from foo ;
str
-
one
two
two
red
(4 rows)
test=> select str from bar ;
str
red
orange
yellow
green
while the topic of replication is on, i'd like to ask if anyone has
implimented networked block level mirroring with eNBD
http://www.it.uc3m.es/~ptb/nbd/ for postgres. specifically i'm speaking of
replication for the purposes of high availability, but i'm also interested
in query performance scalin
