Magnus Hagander wrote:
> Bruce Momjian wrote:
>> Bruce Momjian wrote:
>>> Thanks for the review, Magnus. I have adjusted the patch to use the
>>> same mutex every time the counter is accessed, and adjusted the
>>> pqsecure_destroy() call to properly decrement in the right place.
>>>
>>> Also, I re
Bruce Momjian wrote:
> Bruce Momjian wrote:
>> Thanks for the review, Magnus. I have adjusted the patch to use the
>> same mutex every time the counter is accessed, and adjusted the
>> pqsecure_destroy() call to properly decrement in the right place.
>>
>> Also, I renamed the libpq global destroy
Bruce Momjian wrote:
> Thanks for the review, Magnus. I have adjusted the patch to use the
> same mutex every time the counter is accessed, and adjusted the
> pqsecure_destroy() call to properly decrement in the right place.
>
> Also, I renamed the libpq global destroy function to be clearer
> (t
Russell Smith wrote:
> Tom Lane wrote:
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> >
> >> Bruce Momjian wrote:
> >>
> >>> This is not something we would typically backpatch because of the danger
> >>> of introducing some unexpected change in libpq. We can provide a patch
> >>> to anyo
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>
>> Bruce Momjian wrote:
>>
>>> This is not something we would typically backpatch because of the danger
>>> of introducing some unexpected change in libpq. We can provide a patch
>>> to anyone who needs it, or if the community
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Bruce Momjian wrote:
>> This is not something we would typically backpatch because of the danger
>> of introducing some unexpected change in libpq. We can provide a patch
>> to anyone who needs it, or if the community wants it backpatched I can
>> certa
Bruce Momjian wrote:
> Russell Smith wrote:
> > Will this be back patched when it's committed?
>
> This is not something we would typically backpatch because of the danger
> of introducing some unexpected change in libpq. We can provide a patch
> to anyone who needs it, or if the community wants
Russell Smith wrote:
> Bruce Momjian wrote:
> > Yes, my defines were very messed up; updated version attached.
> >
> Hi,
>
> I've not done a review of this patch, however I did backport it to 8.3
> (as attached in unified diff). The patch wasn't made for PG purposes, so
> it's not in context d
Bruce Momjian wrote:
> Yes, my defines were very messed up; updated version attached.
>
Hi,
I've not done a review of this patch, however I did backport it to 8.3
(as attached in unified diff). The patch wasn't made for PG purposes, so
it's not in context diff. I tested the backported patch an
Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > Thanks for the review, Magnus. I have adjusted the patch to use the
> > same mutex every time the counter is accessed, and adjusted the
> > pqsecure_destroy() call to properly decrement in the right place.
> >
> > Also, I renamed the libpq globa
Bruce Momjian wrote:
> Thanks for the review, Magnus. I have adjusted the patch to use the
> same mutex every time the counter is accessed, and adjusted the
> pqsecure_destroy() call to properly decrement in the right place.
>
> Also, I renamed the libpq global destroy function to be clearer
> (
Magnus Hagander wrote:
> > Your analysis of this problem is right on target. When the SSL
> > callbacks were implemented for threaded libpq, there was never any
> > thought on the effect of unloading libpq while the callbacks were still
> > registered.
> >
> > The attached patch unregisters the c
Bruce Momjian wrote:
> Russell Smith wrote:
>> Alvaro Herrera wrote:
>>> PoolSnoopy wrote:
>>>
***PUSH***
this bug is really some annoyance if you use automatic build environments.
I'm using phpunit to run tests and as soon as postgres is involved the php
cli environment
Russell Smith wrote:
> Alvaro Herrera wrote:
> > PoolSnoopy wrote:
> >
> >> ***PUSH***
> >>
> >> this bug is really some annoyance if you use automatic build environments.
> >> I'm using phpunit to run tests and as soon as postgres is involved the php
> >> cli environment segfaults at the end. t
14 matches
Mail list logo
