| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | phd2(at)earthling(dot)net |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] VACUUM ANALYZE problem on linux |
| Date: | 1999-02-24 18:35:05 |
| Message-ID: | 14890.919881305@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Oleg Broytmann <phd(at)sun(dot)med(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Gowin | 1999-02-24 19:30:11 | RE: [HACKERS] VACUUM ANALYZE problem on linux |
| Previous Message | Bruce Momjian | 1999-02-24 17:32:34 | Re: [HACKERS] One I've never seen before: |