| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| 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 20:40:25 |
| Message-ID: | 19637.1136320825@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2006-01-03 20:47:25 | Re: BUG #2139: Problem when calling functions without any argument |
| Previous Message | Jaime Casanova | 2006-01-03 20:27:52 | Re: BUG #2138: Feature request: handle foreign key constraints on arrays |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-03 20:47:04 | Re: TODO item: list prepared queries |
| Previous Message | Neil Conway | 2006-01-03 20:35:05 | Re: TODO item: list prepared queries |