Re: [HACKERS] Everything leaks; How it mm suppose to work? - Mailing list pgsql-hackers

From Vadim B. Mikheev
Subject Re: [HACKERS] Everything leaks; How it mm suppose to work?
Date
Msg-id 35278977.BFC88880@sable.krasnoyarsk.su
Whole thread Raw
In response to Re: [HACKERS] Everything leaks; How it mm suppose to work?  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian wrote:
>
> Then I ran profiling on the two queries I mentioned, where one leaks and
> one doesn't, and found that the leaking one had 500 extra calls to
> malloc.  Grep'ing out the calls and comparing the output of the two
> profiles, I found:
>
>                 0.00        0.00       1/527         ___irs_gen_acc [162]
>                 0.00        0.00      35/527         _GetDatabasePath [284]
>                 0.00        0.00     491/527         _GetDatabaseName [170]
> [166]    0.8    0.00        0.00     527         _strdup [166]
>                 0.00        0.00     527/2030        _malloc [105]
>                 0.00        0.00     527/604         _strlen [508]
>                 0.00        0.00     527/532         _bcopy [515]
>
> I believe this code was modified by Vadim to fix our problem with blind
> write errors when using psql while the regression tests were being run.
>
> Am I correct on this?  I have not developed a fix yet.

Only src/backend/storage/smgr/md.c:mdblindwrt() was changed...

Vadim

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [QUESTIONS] pqexec error in psql when root creates table (fwd)
Next
From: "Maurice Gittens"
Date:
Subject: On improving OO support in posgresql and relaxing oid bottleneck at the same time