From: | Daniel Migowski <dmigowski(at)ikoffice(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #13800: There is no UNLOAD command |
Date: | 2015-12-07 05:42:51 |
Message-ID: | 41ED3F5450C90F4D8381BC4D8DF6BBDC952DC869@EXCHANGESERVER.ikoffice.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thanks for that explanation.
I need to restart the server because on Windows I can't overwrite the DLL while it is loaded. So I have to restart the server every time. And because of my paying customers I have to do coding on Windows.
Regards,
Daniel Migowski
-----Ursprüngliche Nachricht-----
Von: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Gesendet: Sonntag, 6. Dezember 2015 16:58
An: Daniel Migowski <dmigowski(at)ikoffice(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Betreff: Re: [BUGS] BUG #13800: There is no UNLOAD command
dmigowski(at)ikoffice(dot)de writes:
> While creating extensions in C it is very cumbersome to disconnect,
> restart, connect everytime I recompile my C stuff.
Why would you need to restart? Just starting a fresh connection ought to be enough.
There's pretty much no chance UNLOAD will ever happen, so don't hold your breath waiting. We lack any defined method, for example, for extensions to disconnect from function hooks once they've inserted something in them.
(Reversing what was done at LOAD time wouldn't work, since it'd break any subsequent attachments to the same hook.) Custom GUCs would be another big problem to reverse out, and if I'd consumed any caffeine yet today I could probably name several other trouble spots. It's not insoluble, perhaps, but the amount of work required seems far out of proportion to the benefits.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2015-12-07 05:57:54 | Re: BUG #13800: There is no UNLOAD command |
Previous Message | Pravin Carvalho | 2015-12-06 18:26:33 | Re: BUG #13801: Error while starting psql |