pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: David Rowley <dgrowleyml@gmail.com>
To: Edmund Horner <ejrh00@gmail.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Tid scan improvements
Date: Mon, 7 Jun 2021 21:38:20 +0200
Message-ID: <f4accbba-15db-4a21-175b-947317d13acd@enterprisedb.com> (raw)
In-Reply-To: <CAApHDvqqqHk_rZgtHUv_AJgrt5WFLZk=1gO--8gmRAQbrNWDGA@mail.gmail.com>
References: <CAMyN-kCX8kNy85_Sa-=gXNhZL84vbDtxpKPTF7qTDtTwykaOEQ@mail.gmail.com>
	<CAApHDvqZcqVgWy1nY6xnQpVExtfx=DSKCdXbBxT_b5hQOgu2dA@mail.gmail.com>
	<CAApHDvozoYzeBqzVss_oh5HUFFSMZ2afmQQka-wH4xHU2LUE1w@mail.gmail.com>
	<20210203211919.u7q3vq24g4pd63gv@alap3.anarazel.de>
	<CAApHDvqDcx3_CM1Y4hiCv7q3o3iLFsF1g=SQ5B=6NJoSPEDA_Q@mail.gmail.com>
	<CAApHDvrdoop-9ojBMLX0x_xa0=6v_trhXM8soAwSb5yebaWPgg@mail.gmail.com>
	<CAApHDvor_H6qRrCHXpQKODZaS7L1hU5ogyBGGx3cxLiNgiDhdw@mail.gmail.com>
	<20210216220522.3sn64ui3prwm43zh@alap3.anarazel.de>
	<CAApHDvqfLgx4xaYcJg3wgnW-fe2B-qLUKt00rkPz7QMunQL6+A@mail.gmail.com>
	<CAApHDvqoO33Em0tWoJvwN2cqvAJ45nB+qqfS5cxLbQ45BGPwkg@mail.gmail.com>
	<CAApHDvrxaKMBrV-Tr3ogLaNJMSPC7_GGQWprsDg+HA3Ky0=m=g@mail.gmail.com>
	<05b070ee-b68c-56ca-be41-aa240ee62d81@enterprisedb.com>
	<CAMyN-kAH1e3Wd6GYsV=N6z8_P1TSUHn4D6FTJnw-GEy91i9UYQ@mail.gmail.com>
	<CAApHDvqqqHk_rZgtHUv_AJgrt5WFLZk=1gO--8gmRAQbrNWDGA@mail.gmail.com>

On 07.06.21 13:50, David Rowley wrote:
> On Mon, 7 Jun 2021 at 23:46, Edmund Horner <ejrh00@gmail.com> wrote:
>>
>> On Mon, 7 Jun 2021 at 22:11, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
>>>
>>> This patch didn't add _outTidRangePath() even though we have outNode()
>>> coverage for most/all path nodes.  Was this just forgotten?  See
>>> attached patch.
>>
>>
>> Yes, it looks like an omission.  Thanks for spotting it.  Patch looks good to me.
> 
> Yeah. That was forgotten.  Patch also looks fine to me.  Do you want
> to push it, Peter?

done





view thread (97+ messages)

Message-ID: <f4accbba-15db-4a21-175b-947317d13acd@enterprisedb.com>
Permalink:  ../f4accbba-15db-4a21-175b-947317d13acd@enterprisedb.com/
Also on:    postgresql.org/message-id/f4accbba-15db-4a21-175b-947317d13acd@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@enterprisedb.com, dgrowleyml@gmail.com, ejrh00@gmail.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: Tid scan improvements
  In-Reply-To: <f4accbba-15db-4a21-175b-947317d13acd@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox