| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg13.2: invalid memory alloc request size NNNN |
| Date: | 2021-02-13 11:35:07 |
| Message-ID: | CAM-w4HNzCQeq+qij4oGNGXYmNykD249JTht7DPRER3T1MQySgA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I think to get a size of -4 you would be trying to read a varlena
pointer pointing to four nul bytes. I bet if you run dd on the
corresponding block you'll find a chunk of nuls in the page. That
perhaps makes sense with ZFS where if a new page was linked to the
tree but never written it would be an uninitialized page rather than
the old data.
I'm becoming increasingly convinced that there are a lot of storage
systems out there that just lose data whenever they crash or lose
power. Systems that are supposed to be better than that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2021-02-13 11:35:34 | Re: [HACKERS] GSoC 2017: Foreign Key Arrays |
| Previous Message | Amit Kapila | 2021-02-13 10:49:43 | Re: logical replication seems broken |