| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Magnus Hagander <mha(at)sollentuna(dot)net>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [pgadmin-hackers] Client-side password encryption |
| Date: | 2005-12-21 19:51:46 |
| Message-ID: | 200512211951.jBLJpka03606@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andreas Pflug wrote:
> Martijn van Oosterhout wrote:
>
> >
> > So it's only an issue if you have a policy of removing old versions of
> > libpq on upgrades... I'm not sure what's "best practice" on windows in
> > this area.
>
> When removing the application (in this case: pgsql), you'd remove that
> old lib as well if it's the only app using it. If you have another
> application installed, the deinstaller should observe this, and keep the
> version.
>
>
> I'm voting +1 for lib name versions.
If you add a version number to the Win32 libpq name, you have to update
any command-line compile tools that mention libpq after an upgrade. The
Unix linker knows about version numbers, but the Win32 linker doesn't,
so adding version numbers does add quite a bit of chaos to the Win32
compile world.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2005-12-21 20:16:06 | Re: [pgadmin-hackers] Client-side password encryption |
| Previous Message | Jim C. Nasby | 2005-12-21 19:41:46 | Re: Function call with offset and limit |