Re: database crash during pgbench run
Greg Clough writes: >>> 2018-12-10 19:11:56 IST 23647 LOG: received fast shutdown request >>> any idea what can cause it ? >> Something sent SIGINT to the postmaster. > My money is on the OoM (Out of Memory) killer. That usually uses SIGKILL. If I had to guess, I'd wonder whether the postmaster was manually started, and if so whether it was properly dissociated from the user's terminal (with nohup or the like). If it wasn't, then a control-C typed at the terminal would SIGINT the postmaster as well as whatever it was meant to terminate. regards, tom lane
Re: Database size 1T but unclear why
On Sun, Dec 09, 2018 at 10:01:08AM -0600, Justin Pryzby wrote: > On Sun, Dec 09, 2018 at 05:18:55PM +0200, Mariel Cherkassky wrote: > > I'm trying to understand why my database consume so much space. I checked > > the space it consume on disk : To find single relations which are using more than 100GB, you could also run: |find /base/17312 -name '*.[0-9]??' (technically that should be a regex and not a shell glob but seems to work well enough). Justin
RE: database crash during pgbench run
> > 2018-12-10 19:11:56 IST 23647 LOG: received fast shutdown request > > any idea what can cause it ? > >Something sent SIGINT to the postmaster. My money is on the OoM (Out of Memory) killer. The standard PDGD install on CentOS should disable that, but I'm not sure what OS you're on or how PostgreSQL was installed. Greg Clough. This e-mail, including accompanying communications and attachments, is strictly confidential and only for the intended recipient. Any retention, use or disclosure not expressly authorised by IHSMarkit is prohibited. This email is subject to all waivers and other terms at the following link: https://ihsmarkit.com/Legal/EmailDisclaimer.html Please visit www.ihsmarkit.com/about/contact-us.html for contact information on our offices worldwide.
