| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bad Data back Door |
| Date: | 2012-10-08 18:23:05 |
| Message-ID: | CDFDCFD7-4EFA-437A-9424-B04AD0B2C021@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 8, 2012, at 11:13 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> FWIW, I believe that dblink does not check encoding.
>
> In dblink's case, that boils down to trusting a remote instance of
> Postgres to get this right, which doesn't seem totally unreasonable.
> But I wouldn't object to adding checks there if someone wanted to submit
> a patch.
Yeah, I found this because we had a dblink to another PostgreSQL server's table with data populated from oracle_fdw. I guess trusting is reasonable, though.
I wonder about dbi-link, though…
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-10-08 18:29:07 | Re: Bad Data back Door |
| Previous Message | Tom Lane | 2012-10-08 18:13:52 | Re: Bad Data back Door |