Postgres Pro
Downloads
Home   >   mailing lists

Re: Selecting large tables gets killed - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: Selecting large tables gets killed
Date
Msg-id CABOikdMAqxtROGdVpZRxGfaAyh0NRxw2kJw_vCZhzqOnj-9FMA@mail.gmail.com
Whole thread Raw
In response to Re: Selecting large tables gets killed  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Responses Re: Selecting large tables gets killed  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
List pgsql-hackers
Tree view



On Thu, Feb 20, 2014 at 2:32 PM, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com> wrote:


May be each setup has it's own breaking point. So trying with larger number might reproduce the issue.

I tried to debug it with gdb, but all it showed me was that psql received a SIGKILL signal. I am not sure why.


Is the psql process running out of memory ? AFAIK OOM killer sends SIGKILL. 

Thanks,
Pavan
  
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee

pgsql-hackers by date:

Previous
From: Ian Lawrence Barwick
Date:
Subject: Re: Selecting large tables gets killed
Next
From: Christian Kruse
Date:
Subject: Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication