Re: Ideas for easier debugging of backend problems
От | Jim C. Nasby |
---|---|
Тема | Re: Ideas for easier debugging of backend problems |
Дата | |
Msg-id | 20051027173834.GH63747@pervasive.com обсуждение исходный текст |
Ответ на | Re: Ideas for easier debugging of backend problems (Martijn van Oosterhout <kleptog@svana.org>) |
Список | pgsql-hackers |
On Thu, Oct 27, 2005 at 07:20:57PM +0200, Martijn van Oosterhout wrote: > On Thu, Oct 27, 2005 at 01:13:37PM -0400, Douglas McNaught wrote: > > "Jim C. Nasby" <jnasby@pervasive.com> writes: > > > > > It would also be useful to be able to force the backend to > > > dump core so you can see if it's actually working (granted, I know you > > > can end up hitting the ulimit depending on how much memory is being > > > consumed). Maybe there is a way to do this already and I just don't know > > > it... > > > > SIGABRT? > > Still doesn't do anything if core dumps are disabled. The point is to > enable the user to enable core dumps from the frontend, rather than > having to fiddle the backend environment directly... Actually, SIGABRT is what I was looking for... I wanted a way to force a backend to dump core so I could see if a corefile would actually be generated. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
В списке pgsql-hackers по дате отправления: