Re: [HACKERS] Interval for launching the table sync worker - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Interval for launching the table sync worker
Date
Msg-id 0c475de6-cbc2-1ec6-2b40-6a21113807de@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Interval for launching the table sync worker  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: [HACKERS] Interval for launching the table sync worker
Re: [HACKERS] Interval for launching the table sync worker
List pgsql-hackers
On 4/13/17 06:23, Masahiko Sawada wrote:
> Attached the latest patch. It didn't actually necessary to change
> GetSubscriptionNotReadyRelations. I just changed the logic refreshing
> the sync table state list.

I think this was the right direction, but then I got worried about
having a loop within a loop to copy over the last start times.  If you
have very many tables, that could be a big nested loop.

Here is an alternative proposal to store the last start times in a hash
table.

(We also might want to lower the interval for the test suite, because
there are intentional failures in there, and this patch or one like it
will cause the tests to run a few seconds longer.)

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Keith Fiske
Date:
Subject: Re: [HACKERS] Passing values to a dynamic background worker
Next
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Inadequate parallel-safety check for SubPlans