| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Jakub Glapa <jakub(dot)glapa(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dsa_allocate() faliure |
| Date: | 2018-11-27 08:02:29 |
| Message-ID: | CAEepm=0_7TkVJq6z=-gw2236_mYgY4rRczrtf3ozFKcHW4FHEQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On Tue, Nov 27, 2018 at 4:00 PM Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> Hmm. I will see if I can come up with a many-partition torture test
> reproducer for this.
No luck. I suppose one theory that could link both failure modes
would a buffer overrun, where in the non-shared case it trashes a
pointer that is later dereferenced, and in the shared case it writes
past the end of allocated 4KB pages and corrupts the intrusive btree
that lives in spare pages to track available space.
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edmund Horner | 2018-11-27 08:16:46 | Re: Tid scan improvements |
| Previous Message | Iwata, Aya | 2018-11-27 07:42:10 | RE: libpq debug log |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sanyo Moura | 2018-11-27 14:16:41 | Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |
| Previous Message | Thomas Munro | 2018-11-27 03:00:34 | Re: dsa_allocate() faliure |