Is there a way to do a "warm" backup on a postgres database? (That would be
rolling transactions from one database into a duplicate of it on another
machine.)
I'd like some kind of live backup on the database with no data loss.
Thanks,
Neil
The process still has an open file handle, and will continue to do so even
after you move it. So, if your file is /var/log/messages, and you do a mv
/var/log/messages /var/log/messages.old or something (I know that's stupid,
but this is an example), the process will continue to write to
/var/log/
Never mind. Out of disk space. And the database is fine.
Whew!
-Original Message-
From: Neil Toronto [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 09, 2000 9:49 AM
To: [EMAIL PROTECTED]
Subject: [ADMIN] pg_log
Okay, this is weird.
I've got a server-side program that op
Okay, this is weird.
I've got a server-side program that opens a backend connection to a postgres
6.5.2 database that came with Red Hat 6.1. It issues the following
statements:
BEGIN;
DECLARE qbdbportal CURSOR FOR SELECT next_number from counter WHERE name =
'local';
FETCH ALL IN qbdbportal;
CL
I've installed postgres 6.5.2 on Red Hat Linux 6.1 (kernel 2.2.12).
Whenever I try a "\d" in psql, I get the following error:
ERROR: cache lookup for userid 101 failed
User 101 is postgres. This doesn't happen when I install postgres from the
RPM's. I can't find this anywhere, and looking at
Has anyone clustered a Postgres database server - e.g. made it run on two
seperate machines? (The ideal solution would be a high-availability
cluster, where one machine could take the load of both of the other went
down.)
Any ideas?
Thanks,
Neil
Maybe a good measure of how often the database needs to be vacuumed is how
often the administrators currently vacuum it?
For instance, if it's being vacuumed less than once a day, it may be
perfectly acceptable to vacuum it once early in the morning when nobody is
using it - assuming nobody uses
That usually happens when a process is in "uninterruptible sleep." ps shows
its status as D, and you can't kill it in any way. Uninterruptible sleep
generally happens when a hardware driver is waiting on I/O from some
hardware device.
It's uninterruptible because the I/O is happening in kernel
r Galbavy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 06, 2000 9:19 AM
To: Neil Toronto; [EMAIL PROTECTED]
Subject: Re: [ADMIN] Firewall setup
> Voila! You have yourself an ultra-secure site, as long as you properly
lock
> down your firewall (turn off telnet, ftp, etc.).
Not trying t
On the other hand, you may want to secure things a little bit more. Make
yourself an ultra-locked-down firewall (like a Linux firewall doing nothing
but IP masquerade - very nice) that disallows all incoming packets from its
routable IP, except for those destined for port 80. Forward every
conne
10 matches
Mail list logo
