On Thu, Feb 4, 2021 at 9:36 AM Bharath Rupireddy <bharath.rupireddyforpostg...@gmail.com> wrote: > > On Wed, Feb 3, 2021 at 4:22 PM Fujii Masao <masao.fu...@oss.nttdata.com> > wrote: > > Maybe my explanation in the previous email was unclear. What I think is; If > > the server-level option is explicitly specified, its setting is used > > whatever GUC is. On the other hand, if the server-level option is NOT > > specified, GUC setting is used. For example, if we define the server as > > follows, GUC setting is used because the server-level option is NOT > > specified. > > > > CREATE SERVER loopback FOREIGN DATA WRAPPER postgres; > > > > If we define the server as follows, the server-level setting is used. > > > > CREATE SERVER loopback FOREIGN DATA WRAPPER postgres OPTIONS > > (keep_connections 'on'); > > Attaching v20 patch set. Now, server level option if provided > overrides the GUC.The GUC will be used only if server level option is > not provided. And also, both server level option and GUC are named the > same - "keep_connections". > > Please have a look.
Attaching v21 patch set, rebased onto the latest master. With Regards, Bharath Rupireddy. EnterpriseDB: http://www.enterprisedb.com
v21-0002-postgres_fdw-add-keep_connections-GUC-to-not-cac.patch
Description: Binary data
v21-0003-postgres_fdw-server-level-option-keep_connection.patch
Description: Binary data
