Re: [HACKERS] Patching dblink.c to avoid warning about open - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: [HACKERS] Patching dblink.c to avoid warning about open
Date
Msg-id 200510081530.j98FU2224986@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Patching dblink.c to avoid warning about  (Joe Conway <mail@joeconway.com>)
Responses Re: [HACKERS] Patching dblink.c to avoid warning about  (Joe Conway <mail@joeconway.com>)
List pgsql-patches
Joe Conway wrote:
> Bruce Momjian wrote:
> > There was also a problem in that if two cursors were opened, the first
> > close would close the transaction.  I have fixed that code by changing
> > the xact variable in to a counter that keeps track of the number of
> > opened cursors and commits only when they are all closed.
> >
> > Both the dblink.c patch and the regression patch are at:
> >
> >     ftp://candle.pha.pa.us/pub/postgresql/mypatches
> >
>
> OK, I'll take a look, but I won't have time for a couple of days (I'm
> not at home -- visiting my dad for his 80th birthday -- and have no
> broadband access).

No problem -- thanks.  I have slimmed down the patch by applying the
cosmetic parts to CVS.  Use the URL above to get the newest versions of
the dblink.c and regression changes.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: [HACKERS] Kerberos brokenness and oops question in 8.1beta2
Next
From: Martijn van Oosterhout
Date:
Subject: [PATCH] Using pread instead of lseek (with analysis)