Re: [BUGS] BUG #2129: dblink problem - Mailing list pgsql-patches

From Joe Conway
Subject Re: [BUGS] BUG #2129: dblink problem
Date
Msg-id 43BB0DC8.6080805@joeconway.com
Whole thread Raw
In response to Re: [BUGS] BUG #2129: dblink problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tom Lane wrote:
> Joe Conway <mail@joeconway.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



pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgcrypto: bug in gen_salt (md5/xdes)
Next
From: Stephen Frost
Date:
Subject: TRUNCATE, VACUUM, ANALYZE privileges