| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
| Cc: | Claudio Freire <klaussfreire(at)gmail(dot)com>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com>, PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vacuum: allow usage of more than 1GB of work mem |
| Date: | 2016-12-27 13:54:42 |
| Message-ID: | 20161227135442.jnvir7gunaec2n26@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Anastasia Lubennikova wrote:
> I ran configure using following set of flags:
> ./configure --enable-tap-tests --enable-cassert --enable-debug
> --enable-depend CFLAGS="-O0 -g3 -fno-omit-frame-pointer"
> And then ran make check. Here is the stacktrace:
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x00000000006941e7 in lazy_vacuum_heap (onerel=0x1ec2360,
> vacrelstats=0x1ef6e00) at vacuumlazy.c:1417
> 1417 tblk =
> ItemPointerGetBlockNumber(&seg->dead_tuples[tupindex]);
This doesn't make sense, since the patch removes the "tupindex"
variable in that function.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-12-27 14:03:49 | Re: pg_stat_activity.waiting_start |
| Previous Message | Anastasia Lubennikova | 2016-12-27 13:41:45 | Re: Vacuum: allow usage of more than 1GB of work mem |