Re: Questions and experiences writing a Foreign Data Wrapper

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Questions and experiences writing a Foreign Data Wrapper
Date: 2011-07-23 15:05:12
Message-ID: 2884.1311433512@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> In that case I think I'm in favor of the suggestion of an implied empty
> user mapping for PUBLIC, as long as it can be overridden.

But how would you do that (override it)? All you can do is create an
explicit mapping, and then you still have a mapping that allows access
to PUBLIC. (Or not, but if an empty one does, you're stuck.)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-07-23 15:08:52 Re: [GENERAL] Dropping extensions
Previous Message Tom Lane 2011-07-23 14:58:37 Re: Questions and experiences writing a Foreign Data Wrapper