Thread
-
Re: [HACKERS] VACUUM ANALYZE problem on linux
Tom Lane <tgl@sss.pgh.pa.us> — 1999-02-24T14:56:52Z
Oleg Broytmann <phd@sun.med.ru> writes: > I have compiled with -g, but postgres didn't produce core. Do I need > something special on startup to generate core on crash? Ordinarily not, but perhaps you have a shell 'limit' setting in place that prevents a corefile from being made? I think csh has such a setting but I forget the details. Anyway, if postmaster is started from a shell with any limit variables enabled, they will apply to the backends too. Or you might just not be looking in the right place. Backend crashes produce corefiles in the database subdirectory, eg, /usr/local/pgsql/data/base/MyDatabase/core regards, tom lane
-
Re: [HACKERS] VACUUM ANALYZE problem on linux
Oleg Broytmann <phd@sun.med.ru> — 1999-02-24T15:03:11Z
Hi! On Wed, 24 Feb 1999, Tom Lane wrote: > Oleg Broytmann <phd@sun.med.ru> writes: > > I have compiled with -g, but postgres didn't produce core. Do I need > > something special on startup to generate core on crash? > > Ordinarily not, but perhaps you have a shell 'limit' setting in place > that prevents a corefile from being made? I think csh has such a I am using bash all the time. > setting but I forget the details. Anyway, if postmaster is started from > a shell with any limit variables enabled, they will apply to the > backends too. Ok, I'll retest this. > Or you might just not be looking in the right place. Backend crashes > produce corefiles in the database subdirectory, eg, > /usr/local/pgsql/data/base/MyDatabase/core I search with find / -name core. I got /dev/core and /usr/src/linux/.../core :) Oleg. ---- Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net Programmers don't die, they just GOSUB without RETURN. -
Re: [HACKERS] VACUUM ANALYZE problem on linux
Vince Vielhaber <vev@michvhf.com> — 1999-02-24T15:28:48Z
On Wed, 24 Feb 1999, Oleg Broytmann wrote: > > Or you might just not be looking in the right place. Backend crashes > > produce corefiles in the database subdirectory, eg, > > /usr/local/pgsql/data/base/MyDatabase/core > > I search with find / -name core. I got /dev/core and > /usr/src/linux/.../core :) Try this instead: # find / -name '*.core' and you should find the other core dumps. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include <std/disclaimers.h> TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== -
Re: [HACKERS] VACUUM ANALYZE problem on linux
Oleg Broytmann <phd@sun.med.ru> — 1999-02-24T15:47:11Z
Hi! I ran postmaster from command line (usually I run it from /etc/init.d/), connected to it and ran VACUUM ANALYZE. It worked. I don't know should I use :) or :( - it failed on production server and worked on debugging server... Oleg. ---- Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net Programmers don't die, they just GOSUB without RETURN. -
Re: [HACKERS] VACUUM ANALYZE problem on linux
Oleg Broytmann <phd@sun.med.ru> — 1999-02-24T15:58:29Z
Followup to myself... On Wed, 24 Feb 1999, Oleg Broytmann wrote: > I ran postmaster from command line (usually I run it from /etc/init.d/), > connected to it and ran VACUUM ANALYZE. > It worked. I tested the following way: 1. Run postmaster without parameters; connect and run VACUUM ANALYZE - worked. 2. Run postmaster -b -D/usr/local/pgsql/data -o -Fe and run VACUUM ANALYZE - worked 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. Oleg. ---- Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net Programmers don't die, they just GOSUB without RETURN.