| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jan Urbański <wulczer(at)wulczer(dot)org> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Alpha4 release blockers (was Re: wrapping up this CommitFest) |
| Date: | 2011-03-02 13:25:08 |
| Message-ID: | AANLkTi=kAfmgr+iiB_5droaJ5qWYFtgEfPMCuptGO-GM@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 2, 2011 at 6:14 AM, Jan Urbański <wulczer(at)wulczer(dot)org> wrote:
>> That seems to have fixed it, so I have applied the patch. Would you like
>> to supply some comments to got with it?
>
> The comment would be something like
>
> /* XXX it appears that in some circumstantes the reference count of the
> spiexceptions module drops to zero causing a Python assert failure when
> the garbage collector visits the module. This has been observed on the
> buildfarm. To fix this, add an additional ref for the module here. */
>
> I have no idea why the refcount of the module becomes zero, debug prints
> I added on my system were always showing 1.
But does bumping the ref count then create a leak the rest of the time?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-03-02 13:28:43 | Re: Sync Rep v17 |
| Previous Message | Yeb Havinga | 2011-03-02 12:56:20 | Re: Sync Rep v17 |