| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | fredrik(at)f6(dot)nl |
| Cc: | pgsql-bugs(at)postgreSQL(dot)org |
| Subject: | Re: [BUGS] Possible bug in postgres || libpq |
| Date: | 1999-11-11 03:24:15 |
| Message-ID: | 13468.942290655@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
fredrik chabot <fredrik(at)f6(dot)nl> writes:
>> NOTICE: Buffer Leak: [012] (freeNext=-3, freePrev=-3, relname=dsrbk,
>> blockNum=0, flags=0x4, refcount=64 3)
That is a backend bug, without doubt. I fixed a number of problems that
could lead to that message a month or two ago. If you are running a
version older than 6.5.3 it'd be worth upgrading, I think. But there
were some fixes that I didn't risk committing into 6.5.* because they
were too complex to be sure about --- they will have to wait for the
7.0 betatest/release cycle.
> Log included, i know it isn't pretty sql code but it should work right?
Unfortunately this log is quite useless since you didn't supply table
declarations or test data needed to reproduce the problem. So I can't
be sure if my previous fixes take care of your problem or not...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Cusack | 1999-11-11 09:00:21 | unique()ness not always maintained |
| Previous Message | Oliver Fischer | 1999-11-10 20:22:28 | Re: [BUGS] No index support for date/time types? |