This SQL script is called dblink.sql and should exist on both Windows and Unix installations of Postgres in the contrib directory. However, you’ll need to run a SQL script to create the necessary functions to access them from your database. Running the dblink.sql script With Postgres 9.0 and above, the binary modules required for linking across databases are installed by default. I figured I’d write a quick tutorial on how to set this up, in case anyone runs into a similar need. To do this, I’m using a PostgreSQL package called. Those who have recently volunteered to help me build these plans are able to enter in recipes using the current implementation of the site, and I can then quickly run a single SQL query to pull in all new recipes from production into my staging database. In fact, one scenario in particular where this ability comes in handy is creating meal plans. Since the two database schemas are often slightly different, traditional approaches of exporting and importing database dumps simply don’t work very well, and would be cumbersome if I simply wanted to pull in a few rows of data. Recently, I developed a solution to easily facilitate the moving of data between my production database and staging database, as the latter is currently being used to test the re-invention of the site. In fact, KitchenPC uses it exclusively for all its database needs. Those who know me know I’m a huge fan of. It is possible that PostgreSQL is already installed at your site, either because it was included in your operating system distribution or because the system administrator already installed it. Before you can use PostgreSQL you need to install it, of course. DbLink is located in share/contribs/dblink.sql of your PostgreSQL install.To use. DbLink is probably most comparable in structure to SQL Server's OpenRowset.

Postgresql 9.2 install dblink