[ADMIN] HELP! Passwords stuck in passwd file!

2004-02-01 Thread Michael Allman
I am migrating from 7.2 -> 7.4. I can't figure out how to move the crypt()'ed passwords I made with pg_password utility into the pg_shadow table. All I can find in the documentation is (in 7.3 release notes) Remove secondary password file capability and pg_password utility (Bruce) Any ideas

Re: [ADMIN] Forcing connections closed

2004-02-01 Thread Juan Miguel
'kill -9' PID will force all backends to flush cache for no good reason. Note that on most unixes, a plain kill PID will send the term signal, which tells the process to poltely shutdown and release resources. kill -9 is like using a sledge hammer to swat a fly for this. -

Re: [ADMIN] HELP! Passwords stuck in passwd file!

2004-02-01 Thread Bruce Momjian
Michael Allman wrote: > I am migrating from 7.2 -> 7.4. I can't figure out how to move the > crypt()'ed passwords I made with pg_password utility into the pg_shadow > table. All I can find in the documentation is (in 7.3 release notes) > > Remove secondary password file capability and pg_passwo

Re: [ADMIN] HELP! Passwords stuck in passwd file!

2004-02-01 Thread Michael Allman
As a matter of fact, I was able to "hack" passwd file support back in. It wasn't too hard, but if anyone is interested in seeing the patch, e-mail me privately. Michael On Sun, 1 Feb 2004, Bruce Momjian wrote: > Michael Allman wrote: > > I am migrating from 7.2 -> 7.4. I can't figure out how to

Re: [ADMIN] HELP! Passwords stuck in passwd file!

2004-02-01 Thread Bruce Momjian
Michael Allman wrote: > As a matter of fact, I was able to "hack" passwd file support back in. > It wasn't too hard, but if anyone is interested in seeing the patch, > e-mail me privately. Yes, sorry I make problems for you by removing it, but that whole are needed an overhaul and keeping it in ju

[ADMIN] $PGDATA/global hosed but database still there ... what to do?

2004-02-01 Thread Sincero, Arcadio (ASINCERO)
For reasons I have yet to figure out, my "$PGDATA/global" directory was wiped out (as in completely empty).  (I'm sure it has nothing to do with Postgresql itself but has something to do with the way I'm synchronizing the database on one box to a mirror of the database on another box, i.e.

Re: [ADMIN] Routine maintenance - vacuum, analyse and autovacuum

2004-02-01 Thread Iain
> Just moving from 7.1 to 7.4 should help, since you can start using plain (B> vacuum (7.1's vacuum is equivalent to vacuum full IIRC). (B (BThat old DB server has been running contnuously for 2 years they tell me. (BApparently it is also growing despite nightly vacuums and a stable data set (

Re: [ADMIN] Routine maintenance - vacuum, analyse and autovacuum

2004-02-01 Thread Tom Lane
"Iain" <[EMAIL PROTECTED]> writes: >> Just moving from 7.1 to 7.4 should help, since you can start using plain >> vacuum (7.1's vacuum is equivalent to vacuum full IIRC). > That old DB server has been running contnuously for 2 years they tell me. > Apparently it is also growing despite nightly vac

Re: [ADMIN] Routine maintenance - vacuum, analyse and autovacuum

2004-02-01 Thread Iain
(B> Kinda sounds like index bloat to me --- have you done any looking to (B> determine which files are growing? (B> (B (BNo, I havn't. I don't actually have access to that machine, and there is a (Bcirtain reluctance to tamper with it. However Ithink that it will need some (Battention soon.