* Bruce Momjian <[EMAIL PROTECTED]> [010102 01:49]:
> > Looking at Page 166 of "SQL-99 Complete, Really" by Peter Gulutzan &
> > Trudy Peltzer, R&D Books, ISBN 0-87930-568-1, 1st bullet:
>
> That is a strange name for a book. :-)
They explain the title as meaning they don't refer you off to anot
"Travis W. Pouarz" <[EMAIL PROTECTED]> writes:
> Does the regression test the optional interfaces such as tcl and odbc?
No, just the core code (and even there, the coverage is pretty limited,
but it's a lot better than nothing...)
> Here are the fails:
> timestamp... FAILED
> t
Hello,
I've found a memory leak in libecpg of PostgreSQL 7.0.3.
The leak is caused by the memory allocation in
src/interfaces/ecpg/lib/execute.c in line 669 which is never freed.
Adding a "free(array_query);" after PQexec in line 671 seems to fix the
leak.
Regards
Thorsten
--
E-M
On Mon, 1 Jan 2001, Tom Lane wrote:
> Running the regression tests (src/test/regress) would be a more thorough
> test that things are working.
Right.
Does the regression test the optional interfaces such as tcl and odbc?
Here are the fails:
timestamp... FAILED
test geometry
Travis W. Pouarz writes:
> ar crs libpgtcl.a pgtcl.o pgtclCmds.o pgtclId.o
> touch libpgtcl.a
> ../../../src/backend/port/aix/mkldexport.sh libpgtcl.a > libpgtcl.exp
> cc -O -qtune=p2sc -qmaxmem=8192 -Wl,-H512 -Wl,-bM:SRE
> -Wl,-bI:../../../src/backend/postgres.imp -Wl,-bE:libpgtcl.exp -o
> libpg
Yes, I see the problem you reported. Here is the patch I have applied.
Thanks.
> Hello,
>
> I've found a memory leak in libecpg of PostgreSQL 7.0.3.
> The leak is caused by the memory allocation in
> src/interfaces/ecpg/lib/execute.c in line 669 which is never freed.
> Adding a "free(array_que
On Mon, 1 Jan 2001, Tom Lane wrote:
>[EMAIL PROTECTED] writes:
>> Problem 1: "vacuum messages;" works but "vacuum analyze messages;"
>> kills the backend.
>
>We have absolutely no hope of responding to a bug report with only
>that amount of information. How about a backtrace from the core
>file?
