pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Grigory Smolkin <g.smolkin@postgrespro.ru>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: Don't try fetching future segment of a TLI.
Date: Tue, 7 Apr 2020 12:36:18 +0300
Message-ID: <c3f1c0f6-5e57-9b47-7dff-a21e760920b8@postgrespro.ru> (raw)
In-Reply-To: <20200407081732.GC6655@paquier.xyz>
References: <16159-f5a34a3a04dc67e0@postgresql.org>
	<20191212.124856.202839248708529678.horikyota.ntt@gmail.com>
	<CAEBTBzsi8HrTTSC1xwL0otzrwdefRSLuwdQ7LnAs+jQeN+EJ8A@mail.gmail.com>
	<20200129.120222.1476610231001551715.horikyota.ntt@gmail.com>
	<8c831a30-a3a2-de89-2059-e7ce842d7aed@pgmasters.net>
	<CAEBTBzupObE6Gep1y-ajvUh4AjuvyTmfTewshVOei12uRV=Q8Q@mail.gmail.com>
	<792ea085-95c4-bca0-ae82-47fdc80e146d@oss.nttdata.com>
	<762ffb60-df9c-0efc-2714-9859219157e3@pgmasters.net>
	<3e0713d2-56d2-9883-4213-d5ba7f0dcabf@oss.nttdata.com>
	<20200407081732.GC6655@paquier.xyz>

I`ve bumped into this issue recently:
https://www.postgresql.org/message-id/dd6690b0-ec03-6b3c-6fac-c963f91f87a7%40postgrespro.ru


On 4/6/20 8:43 PM, Fujii Masao wrote:

> The patch looks good to me. Attached is the updated version of the patch.
> I updated only comments.
>
> Barring any objection, I will commit this patch. 

I`ve been running tests on your patch. So far so good.

On Tue, Apr 07, 2020 at 12:15:00PM +0900, Fujii Masao wrote:

> I understood the situation and am fine to back-patch that. But I'm not sure
> if it's fair to do that. Maybe we need to hear more opinions about this?
> OTOH, feature freeze for v13 is today, so what about committing the patch
> in v13 at first, and then doing the back-patch after hearing opinions and
> receiving many +1?

+1 to back-patching it.

-- 
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

view thread (13+ messages)  latest in thread

Message-ID: <c3f1c0f6-5e57-9b47-7dff-a21e760920b8@postgrespro.ru>
Permalink:  ../c3f1c0f6-5e57-9b47-7dff-a21e760920b8@postgrespro.ru/
Also on:    postgresql.org/message-id/c3f1c0f6-5e57-9b47-7dff-a21e760920b8@postgrespro.ru

 · 

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-bugs@postgresql.org
  Cc: g.smolkin@postgrespro.ru, pgsql-bugs@lists.postgresql.org
  Subject: Re: Don't try fetching future segment of a TLI.
  In-Reply-To: <c3f1c0f6-5e57-9b47-7dff-a21e760920b8@postgrespro.ru>

* 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