From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
Cc: | pgsql-patches(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] Auto-reload of dynamic libraries |
Date: | 2002-05-04 15:36:45 |
Message-ID: | 27176.1020526605@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> writes:
> This small patch reloads dynamic libraries whose modification time is
> greater than that at the time it was initially loaded. This means that
> connections do not need to be reinitialised when a library is recompiled.
Is that a good idea? It's easy to imagine cases where a library is not
designed to be unloaded (eg, it hooks into things in the main backend
and doesn't have a way to unhook). I'd rather stick with the current
behavior of unload/reload only when specifically commanded to.
The patch as given fails in the same inode/different path case, btw.
I think you wanted to make the test further down.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-05-04 16:18:24 | Re: Native Windows, Apache Portable Runtime |
Previous Message | Tom Lane | 2002-05-04 15:20:39 | Re: Using views and MS access via odbc |
From | Date | Subject | |
---|---|---|---|
Next Message | Manfred Koizar | 2002-05-05 15:29:24 | Reduce per tuple overhead (bitmap) |
Previous Message | Gavin Sherry | 2002-05-04 11:05:35 | Auto-reload of dynamic libraries |