rces the search_path on the remote
side to be 'pg_catalog', so all objects used in the session
established by postgres_fdw have to be schema-qualified. Trigger
function is executed in such context, so you need to qualify all
objects in your trigger function with schema name, like
'pu
ho is used for the dbtoyaml invocation.
I'm not sure about other object types, but IMO secure information such
as URI which includes password should be stored in user mappings rather
than servers.
Regards,
--
Shigeru Hanada
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
---
Seq Scan on pg_amproc (cost=0.00..4.52 rows=252 width=18) (actual
time=0.008..0.045 rows=252 loops=1)
Total runtime: 0.089 ms
(2 rows)
IMHO planner should be modified so that it can estimate result rows
accurately in this case.
--
Shigeru Hanada
--
Sent via pgsql-genera
]https://sourceforge.net/projects/interdbconnect/
[2]http://archives.postgresql.org/pgsql-hackers/2011-10/msg01329.php
Regards,
--
Shigeru Hanada
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
nfortunately FDW for PostgreSQL won't be shipped with 9.1 release.
Hopefully, PostgreSQL-FDW for 9.1 might be released as an external
module, and then you would be able to replace dblink with foreign tables.
Regards,
--
Shigeru Hanada
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
