| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Semab Tariq <semab(dot)tariq(at)enterprisedb(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Andres Freund <andres(at)anarazel(dot)de>, CM Team <cm(at)enterprisedb(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |
| Date: | 2021-11-05 11:22:36 |
| Message-ID: | 20211105112236.GA711250@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Nov 05, 2021 at 03:21:15PM +0500, Semab Tariq wrote:
> Breakpoint 1, 0x40000000003fcb50:0 in equalTupleDescs (
> tupdesc1=0x40010006f968, tupdesc2=0x87ffffffffffac50)
The addresses there are weird. tupdesc1 is neither a stack address nor a heap
address; it may be in a program text section. tupdesc2 is a stack address.
In the earlier stack trace from
https://postgr.es/m/CANFyU94Xa8a5+4sZ7PxOiDLq+yN89g6y-9nNk-eLEvX6YUXbXA@mail.gmail.com
both tupdesc1 and tupdesc2 were heap addresses.
> /home/pgbfarm/buildroot-gharial-HEAD/postgresql/src/test/subscription/tmp_check/t_080_step_equalTupleDescs_main_data/commands-gdb:8: Error in sourced command file:
> Error accessing memory address 0x40010006f968: Bad address.
Thanks. Please try the attached test version, which avoids exiting too early
like the last version did.
| Attachment | Content-Type | Size |
|---|---|---|
| step-to-crash-v0.2.patch | text/plain | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2021-11-05 11:43:00 | Re: BUG #17257: (auto)vacuum hangs within lazy_scan_prune() |
| Previous Message | Semab Tariq | 2021-11-05 10:21:15 | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |