Subject: Re: pgsql: Improve handling of parameter differences in physical
 replicatio
To: Andres Freund <andres@anarazel.de>,
 Fujii Masao <masao.fujii@oss.nttdata.com>, pgsql-hackers@postgresql.org
References: <E1jIpJu-0007Ql-CL@gemulon.postgresql.org>
 <1f9fb47c-eacc-dc42-3267-20c387fa0a2f@oss.nttdata.com>
 <20200330181030.z5yiftm65mxvr46p@alap3.anarazel.de>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <777fd915-dd1e-3368-47f2-29239de2b2db@2ndquadrant.com>
Date: Tue, 14 Apr 2020 09:17:39 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0)
 Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20200330181030.z5yiftm65mxvr46p@alap3.anarazel.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2020-03-30 20:10, Andres Freund wrote:
> Also, shouldn't dynahash be adjusted as well? There's e.g. the
> following HASH_ENTER path:
> 				/* report a generic message */
> 				if (hashp->isshared)
> 					ereport(ERROR,
> 							(errcode(ERRCODE_OUT_OF_MEMORY),
> 							 errmsg("out of shared memory")));

Could you explain further what you mean by this?  I don't understand how 
this is related.

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