From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: dblink patches for comment |
Date: | 2009-06-01 00:27:32 |
Message-ID: | 4A232074.5020506@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> It's hard to review it without any docs that say what it's supposed to do.
> (And you'd need to patch the docs anyway, eh?)
Here's a much simpler SQL/MED support patch for dblink.
This enforces security in the same manner for FOREIGN SERVER connections
as that worked out over time for other dblink connections. Essentially,
the FOREIGN SERVER and associated user MAPPING provides the needed info
for the libpq connection, but otherwise behavior is the same.
I've also attached a doc patch.
Comments?
Joe
Attachment | Content-Type | Size |
---|---|---|
dblink.2009.05.31.02-sqlmed.diff | text/x-patch | 7.7 KB |
dblink.2009.05.31.02-sqlmed_doc.diff | text/x-patch | 2.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-06-01 02:53:59 | Win32 link() function |
Previous Message | Mark Wong | 2009-06-01 00:08:07 | survey of table blocksize changes |