Re: Default connection parameters for postgres_fdw and dblink

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Default connection parameters for postgres_fdw and dblink
Date: 2013-03-22 19:06:52
Message-ID: 1363979212.21411.4.camel@sussancws0025
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2013-03-22 at 12:19 -0400, Tom Lane wrote:
> Is there a better way to handle all this? It may be too late to rethink
> dblink's behavior anyhow, but perhaps it's not too late to change
> postgres_fdw. I think though that once we let 9.3 out the door, it
> *will* be too late to make any major changes, because postgres_fdw's
> usage is going to go through the roof now that it can do remote updates.

The first thing that occurs to me is to have postgres_fdw install some
GUCs with reasonable defaults.

Perhaps the default could be a magic value that is replaced by the
current user or something (similar to search_path).

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-03-22 19:29:59 Re: postgres_fdw vs data formatting GUCs (was Re: [v9.3] writable foreign tables)
Previous Message Merlin Moncure 2013-03-22 19:05:56 Re: Page replacement algorithm in buffer cache