On Fri, Dec 19, 2014 at 06:52:42PM -0700, David Johnston wrote:
> While the fact that you cannot do:
> 
> [service_template]
> host=xxx.xxx.xxx.xxx
> 
> [service_db1]
> dbname=db1
> service=service_template
> 
> seems obvious there is nothing in the documentation that says this is
> prohibited; and attempting a simple alias entry:

I have developed the attached patch to warn users that nesting of
service entries is not supported.  I prefer code warnings over
documentation because the user gets the warning as soon as they try
something, rather than having to hunt in the documentation.  I don't
think this issue has come up enough to warrant a doc mention too though.

-- 
  Bruce Momjian  <br...@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +
diff --git a/src/interfaces/libpq/fe-connect.c b/src/interfaces/libpq/fe-connect.c
new file mode 100644
index e2a06b3..083e6df
*** a/src/interfaces/libpq/fe-connect.c
--- b/src/interfaces/libpq/fe-connect.c
*************** parseServiceFile(const char *serviceFile
*** 4061,4066 ****
--- 4061,4076 ----
  				}
  				*val++ = '\0';
  
+ 				if (strcmp(key, "service") == 0)
+ 				{
+ 					printfPQExpBuffer(errorMessage,
+ 									  libpq_gettext("nested service specifications not supported in service file \"%s\", line %d\n"),
+ 									  serviceFile,
+ 									  linenr);
+ 					fclose(f);
+ 					return 3;
+ 				}
+ 
  				/*
  				 * Set the parameter --- but don't override any previous
  				 * explicit setting.
-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Reply via email to