Re: Warning "TupleDesc reference leak"

From: Marek Lewczuk <newsy(at)lewczuk(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Lista dyskusyjna pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Warning "TupleDesc reference leak"
Date: 2007-02-23 14:38:03
Message-ID: 45DEFC4B.7060308@lewczuk.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane pisze:
> Marek Lewczuk <newsy(at)lewczuk(dot)com> writes:
>> after suggestions that I should postgres update to the latest (currently
>> I have 8.2.3) I thought that my problem will be solved. But no, it is
>> not - postgres still throws warnings:
>> WARNING: TupleDesc reference leak: TupleDesc 0x41fd7018 (16427,-1)
>> still referenced
>
> Show us a test case please.
Hello Tom,
Thanks for reply. You need a test case, but what it should include ? I
don't know in what situations this warning is thrown. My database is
quite large - hundreds of tables, tons of data... Where I should start ?

Thanks
ML

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robert Haas 2007-02-23 14:39:52 Re: complex referential integrity constraints
Previous Message Alvaro Herrera 2007-02-23 14:34:53 Re: complex referential integrity constraints