RE: [HACKERS] VACUUM ANALYZE problem on linux
Dan Gowin <dgowin@avantec.net>
From: Dan Gowin <DGowin@avantec.net>
To: "'Tom Lane'" <tgl@sss.pgh.pa.us>, phd2@earthling.net
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Date: 1999-02-24T19:30:11Z
Lists: pgsql-hackers
What user ID are you using? Are you "su"ing over the the postgres user ID. Also, make sure all of the environment variables are exported in the script. PGPORT, PGUSER, etc... D. -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Wednesday, February 24, 1999 1:35 PM To: phd2@earthling.net Cc: PostgreSQL-development Subject: Re: [HACKERS] VACUUM ANALYZE problem on linux Oleg Broytmann <phd@sun.med.ru> writes: > 3. Run postmaster -b -D/usr/local/pgsql/data -o -Fe -S (to detach it) > and run VACUUM ANALYZE - worked > (I took these parameters from script /etc/init.d/postgres) > 4. Run /etc/init.d/postgres start > and run VACUUM ANALYZE - failed, no core file. So there is something different about the environment of your postmaster when it's started by init.d versus when it's started by hand. Now you just have to figure out what. I thought of environment variables, ulimit settings, ownership/permission settings ... but it's not clear why any of these would affect VACUUM in particular yet leave you able to do other stuff successfully. Puzzling. regards, tom lane