Обсуждение: Warning "TupleDesc reference leak"
Hello, after upgrade to 8.2 version, PostgreSQL throws following warnings: WARNING: TupleDesc reference leak: TupleDesc 0x42051d90 (16425,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41f60ad0 (16425,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x4203d908 (16425,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41fdc410 (16425,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41fbb568 (16425,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x42044bf0 (16425,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x42038e60 (16425,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41feebc0 (16425,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41fa0018 (16425,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41fd9c30 (16425,-1) still referenced What it means ? Thanks ML
On Tue, 2007-02-20 at 08:55, Marek Lewczuk wrote: > Hello, > after upgrade to 8.2 version, PostgreSQL throws following warnings: > WARNING: TupleDesc reference leak: TupleDesc 0x42051d90 (16425,-1) > still referenced I don't know what that means, but which 8.2 version? 8.2.3 is the latest 8.2 version. If you're not running that update to that first and see if it helps.
Marek Lewczuk wrote: > Hello, > after upgrade to 8.2 version, PostgreSQL throws following warnings: > WARNING: TupleDesc reference leak: TupleDesc 0x42051d90 (16425,-1) > still referenced Are there C functions, or anything interesting which we should know about your database? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Marek Lewczuk wrote: > Hello, > after upgrade to 8.2 version, PostgreSQL throws following warnings: > WARNING: TupleDesc reference leak: TupleDesc 0x42051d90 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41f60ad0 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x4203d908 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41fdc410 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41fbb568 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x42044bf0 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x42038e60 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41feebc0 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41fa0018 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41fd9c30 (16425,-1) > still referenced > > What it means ? there is at least one known cause for that though that is fixed in 8.2.3 and involves plpgsql and subtransactions/exception blocks - what version are you running exactly ? Stefan
Marek Lewczuk pisze: > Hello, > after upgrade to 8.2 version, PostgreSQL throws following warnings: > WARNING: TupleDesc reference leak: TupleDesc 0x42051d90 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41f60ad0 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x4203d908 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41fdc410 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41fbb568 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x42044bf0 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x42038e60 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41feebc0 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41fa0018 (16425,-1) > still referenced > WARNING: TupleDesc reference leak: TupleDesc 0x41fd9c30 (16425,-1) > still referenced > Hello again, 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 WARNING: TupleDesc reference leak: TupleDesc 0x41f42490 (16427,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41fc3490 (16427,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x4200c880 (16427,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x42023400 (16427,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41f48728 (16427,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x4201d728 (16427,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41ffd8b0 (16427,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41fe8370 (16427,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x420329e8 (16427,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x420026b0 (16427,-1) still referenced WARNING: TupleDesc reference leak: TupleDesc 0x41f8de78 (16427,-1) still referenced What does it mean ? Thanks in advance for help. ML
Marek Lewczuk <newsy@lewczuk.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.
regards, tom lane
Tom Lane pisze: > Marek Lewczuk <newsy@lewczuk.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
Marek Lewczuk <newsy@lewczuk.com> writes:
> 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 ?
I doubt it's got anything to do with your data; I'd look at complex
PL functions. If you don't already know which queries trigger it,
increase your logging to find out.
regards, tom lane