| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | mgittens(at)gits(dot)nl (Maurice Gittens) |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] How To free resources used by large object Relations? |
| Date: | 1998-02-20 16:04:16 |
| Message-ID: | 199802201604.LAA04883@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> Hi,
>
> I've changed the large object memory managment strategy to ensure that
> each large object has it's own memory context.
> This way I can free all memory for a large object when I lo_close
> is called for it's oid. This seems to work.
This is a good idea.
>
> I've noticed that the heap_close function used to close the heap used
> by a large object doesn't really do any thing. (It calls RelationClose
> which decrements some reference count).
>
> Somehow I have to free the relation from the cache in the following
> situations:
> 1. In a transaction I must free the stuff when the transaction is
> commited/aborted.
> 2. Otherwise it must happen when lo_close is called.
>
> Is this right?
>
Beats me.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D. Jay Newman | 1998-02-20 16:08:37 | Re: [HACKERS] Who is everybody? |
| Previous Message | Bruce Momjian | 1998-02-20 15:45:30 | Re: [HACKERS] Permissions on copy |