| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | mgittens(at)gits(dot)nl (Maurice Gittens) |
| Cc: | lockhart(at)alumni(dot)caltech(dot)edu, psqlhack(at)maidast(dot)demon(dot)co(dot)uk, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Memory leaks for large objects |
| Date: | 1998-02-18 15:01:16 |
| Message-ID: | 199802181501.KAA15441@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> Large object I/O does not persist across transactions in my case.
> But maybe there are applications which assume that it does. So
> "fixing" it might break things. How about some compile time flag
> which selects between the old behaviour and new behaviour?
> The old behaviour could be the default.
>
> (The new behaviour would simply avoid fiddling with MemoryContexts at all.)
> My current workaround is to reconnect to the database after some
> number of transactions.
Large object have been broken for quite some time. I say remove the
memory context stuff and see what breaks. Can't be worse than earlier
releases, and if there is a problem, it will show up for us and we can
issue a patch.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-02-18 15:08:17 | Re: [HACKERS] ecpg stuff |
| Previous Message | Andrew Martin | 1998-02-18 14:57:07 | Re: [HACKERS] Valid ports for v6.3 |