Robert Haas wrote:
> I'm pretty sure it's the same as this:
> https://commitfest.postgresql.org/action/patch_view?id=263
Yes, (2) are resolved with the patch with a different implementation.
> (2) is fixed by RegisterXactCallback(AtEOXact_dblink). However, there
> might be any better solutions
On Wed, Feb 24, 2010 at 2:33 PM, Bruce Momjian wrote:
> What happened to this patch?
I'm pretty sure it's the same as this:
https://commitfest.postgresql.org/action/patch_view?id=263
...Robert
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscr
What happened to this patch?
---
Itagaki Takahiro wrote:
>
> Merlin Moncure wrote:
>
> > Takahiro wrote:
> > > contrib/dblink seems to have no treatments for query cancels.
> > > (1) Users need to wait for completion of r
Itagaki Takahiro wrote:
> Stephen Frost wrote:
>
>> Can you provide an update on this patch? Joe, you were going to
>> review and possibly commit it. Itagaki, did you have a new version?
>> Are there any outstanding issues?
>
> Thanks for your reviewing.
> Here is an updated version. I f
Stephen Frost wrote:
> Can you provide an update on this patch? Joe, you were going to
> review and possibly commit it. Itagaki, did you have a new version?
> Are there any outstanding issues?
Thanks for your reviewing.
Here is an updated version. I fixed some bugs:
* Fix connection
Joe, Itagaki,
Can you provide an update on this patch? Joe, you were going to
review and possibly commit it. Itagaki, did you have a new version?
Are there any outstanding issues?
Thanks,
Stephen
signature.asc
Description: Digital signature
Merlin Moncure wrote:
> Takahiro wrote:
> > contrib/dblink seems to have no treatments for query cancels.
> > (1) Users need to wait for completion of remote query.
> > (2) PGresult objects will be memory leak.
Here is a patch to fix the issues. I hope the fixes will be ported
to older versions
On Thu, Jun 25, 2009 at 10:41 PM, Itagaki
Takahiro wrote:
> Hi,
>
> contrib/dblink seems to have no treatments for query cancels.
> It causes the following issues:
>
> (1) Users need to wait for completion of remote query.
> Requests for query cancel won't be delivered to remote servers.
>
> (2)
