Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data

From: Semab Tariq <semab(dot)tariq(at)enterprisedb(dot)com>
To: Noah Misch <noah(at)leadboat(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-09 06:55:57
Message-ID: CABimMB7kek5OKfNG53BW_tnM=EU=75_F80xvBjYEpUXQ+3Yuvw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Nov 8, 2021 at 7:46 PM Noah Misch <noah(at)leadboat(dot)com> wrote:

> On Mon, Nov 08, 2021 at 02:09:15PM +0500, Semab Tariq wrote:
> > On Mon, Nov 8, 2021 at 12:09 PM Noah Misch <noah(at)leadboat(dot)com> wrote:
> > > This postgres binary apparently contains an explicit branch to
> > > 0x3fffffffff3fdc30, which is not an address reasonably expected to
> contain
> > > code. (It's not a known heap, a known stack, or a CODE section from
> the
> > > binary file.) This probably confirms a toolchain bug.
> > >
> > > Would you do "git checkout 166f943" in the source directory you've been
> > > testing, then rerun the test and post the compressed
> > > tmp_check/log directory?
> > >
> >
> > So make command fails after I applied the v0.4 patch to 166f943 also it
> did
> > not create any tmp_check/log directory
>
> > t/080_step_equalTupleDescs....Can't locate IPC/Run.pm in @INC (@INC
> contains:
> /home/pgbfarm/buildroot-gharial-HEAD/postgresql/src/test/subscription/../../../src/test/perl
> /home/pgbfarm/buildroot-gharial-HEAD/postgresql/src/test/subscription
> /home/pgbfarm/buildroot-gharial-HEAD/postgresql/src/test/subscription/../../../src/test/perl
> /home/pgbfarm/buildroot-gharial-HEAD/postgresql/src/test/subscription
> /opt/perl_64/lib/5.8.8/IA64.ARCHREV_0-thread-multi-LP64
> /opt/perl_64/lib/5.8.8
> /opt/perl_64/lib/site_perl/5.8.8/IA64.ARCHREV_0-thread-multi-LP64
> /opt/perl_64/lib/site_perl/5.8.8 /opt/perl_64/lib/site_perl
> /opt/perl_64/lib/vendor_perl/5.8.8/IA64.ARCHREV_0-thread-multi-LP64
> /opt/perl_64/lib/vendor_perl/5.8.8 /opt/perl_64/lib/vendor_perl .) at
> /home/pgbfarm/buildroot-gharial-HEAD/postgresql/src/test/subscription/../../../src/test/perl/PostgreSQL/Test/Cluster.pm
> line 102.
>
> It looks like this attempt did not use a shell with the environment
> variables
> discussed upthread.
>

Yes, I missed the trick PFA tmp_check.tar.bz2

--
Thanks & Regards,
Semab

Attachment Content-Type Size
tmp_check.tar.bz2 application/x-bzip2 358.6 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kyotaro Horiguchi 2021-11-09 08:32:48 Re: BUG #17269: Why is virtual memory usage of PostgreSQL growing constantly?
Previous Message 菊池祐 2021-11-09 06:52:51 Re: BUG #17269: Why is virtual memory usage of PostgreSQL growing constantly?