Martin Pihlak wrote:
I wrote:
The validator is run for the generic options specified to CREATE/ALTER FDW,
SERVER and USER MAPPING (+ possible future SQL/MED objects). In this case the
catalog is always known. Also we can assume that the catalog is known, if a
user
runs the validator
I wrote:
The validator is run for the generic options specified to CREATE/ALTER FDW,
SERVER and USER MAPPING (+ possible future SQL/MED objects). In this case the
catalog is always known. Also we can assume that the catalog is known, if a
user
runs the validator directly. So yes, AFAICS
Tom Lane wrote:
The validator function must take two arguments: one of type text[], which
will contain the array of options as stored in the system catalogs, and one
of type oid, which will be the OID of the system catalog containing the
options, or zero if the context is not known.
Hmm,
It appears that the function for validating generic options to a FDW,
SERVER and USER MAPPING is always passed a catalog oid of 0. Whereas
it should actually be passed the oid of the catalog that the options
apply to.
Attached patch fixes the issue by passing the proper catalog id from
Martin Pihlak martin.pih...@gmail.com writes:
It appears that the function for validating generic options to a FDW,
SERVER and USER MAPPING is always passed a catalog oid of 0. Whereas
it should actually be passed the oid of the catalog that the options
apply to.
According to what? I can't
Tom Lane wrote:
According to what? I can't find any documentation whatsoever on what
arguments that function is supposed to get.
regards, tom lane
According to
http://www.postgresql.org/docs/8.4/static/sql-createforeigndatawrapper.html:
The validator function must
Martin Pihlak martin.pih...@gmail.com writes:
Tom Lane wrote:
According to what? I can't find any documentation whatsoever on what
arguments that function is supposed to get.
According to
http://www.postgresql.org/docs/8.4/static/sql-createforeigndatawrapper.html:
The validator function
