| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>, Akio Iwaasa <iwaasa(at)mxs(dot)nes(dot)nec(dot)co(dot)jp> |
| Subject: | Re: [BUGS] BUG #2129: dblink problem |
| Date: | 2006-01-03 23:50:32 |
| Message-ID: | 43BB0DC8.6080805@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>
>>Should I just accept that the cursor advances on a row type mismatch
>>error, fix using the attached patch and adding SCROLL to dblink_open(),
>>or something else? Any opinions out there?
>
> I would go with accepting (and documenting) the cursor advance. Trying
> to undo it seems too risky, and it's not like this is a situation that
> would arise in a properly-debugged application anyway. I can't see
> expending a great amount of effort on it --- protecting against a crash
> seems sufficient.
>
OK -- applied back to 7.3.
Thanks,
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Qingqing Zhou | 2006-01-04 04:23:54 | Re: BUG #2135: system error 182 while loading ODBC driver |
| Previous Message | Tom Lane | 2006-01-03 23:33:50 | Re: Small bug fix in readline promt handling |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2006-01-04 01:19:41 | Inconsistent syntax in GRANT |
| Previous Message | Tom Lane | 2006-01-03 23:47:48 | Re: pgcrypto: bug in gen_salt (md5/xdes) |