Re: Selecting large tables gets killed

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: amul sul <sul_amul(at)yahoo(dot)co(dot)in>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Selecting large tables gets killed
Date: 2014-02-20 09:05:59
Message-ID: CABOikdMAqxtROGdVpZRxGfaAyh0NRxw2kJw_vCZhzqOnj-9FMA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 20, 2014 at 2:32 PM, Ashutosh Bapat <
ashutosh(dot)bapat(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christian Kruse 2014-02-20 09:06:31 Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication
Previous Message Ian Lawrence Barwick 2014-02-20 09:04:42 Re: Selecting large tables gets killed