Re: postgres_fdw batching vs. (re)creating the tuple slots - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: postgres_fdw batching vs. (re)creating the tuple slots
Date
Msg-id cdff37d6-c57c-e40c-4635-4bcaeccd0d7d@enterprisedb.com
Whole thread Raw
In response to Re: postgres_fdw batching vs. (re)creating the tuple slots  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: postgres_fdw batching vs. (re)creating the tuple slots
List pgsql-hackers
On 6/9/21 1:08 PM, Tomas Vondra wrote:
> 
> 
> On 6/9/21 12:50 PM, Bharath Rupireddy wrote:
>> On Wed, Jun 9, 2021 at 4:00 PM Tomas Vondra
>> <tomas.vondra@enterprisedb.com> wrote:
>>>
>>> Hi,
>>>
>>> Here's a v2 fixing a silly bug with reusing the same variable in two
>>> nested loops (worked for simple postgres_fdw cases, but "make check"
>>> failed).
>>
>> I applied these patches and ran make check in postgres_fdw contrib
>> module, I saw a server crash. Is it the same failure you were saying
>> above?
>>
> 
> Nope, that was causing infinite loop. This is jut a silly mistake on my
> side - I forgot to replace the i/j variable inside the loop. Here's v3.
> 
> regards
> 

FWIW I've pushed this, after improving the comments a little bit.


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Replication protocol doc fix
Next
From: Alvaro Herrera
Date:
Subject: Re: pg_stat_progress_create_index vs. parallel index builds