| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: win32 pg_autovacuum make error |
| Date: | 2004-10-16 20:52:29 |
| Message-ID: | 26937.1097959949@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> I don't have a build env around ATM to test, but my guess would be the
> new libpq linking. These functions are probably imported from libpq, and
> therefor must be added to the .def file (or rather the .txt file that
> generates the .def file that Tom just committed if you have the very
> latest-and-greates cvs ver) for libpq.dll.
I have a better idea: make pg_autovacuum not use DLLists. That code
is slated for eventual removal from libpq anyway (if not complete
destruction). Had I been aware that autovacuum was using it I would
have objected ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-10-16 21:18:26 | Re: Getting rid of AtEOXact_Buffers (was Re: [Testperf-general] Re: [PERFORM] First set of OSDL Shared Memscalability results, some wierdness ...) |
| Previous Message | Magnus Hagander | 2004-10-16 20:38:01 | Re: win32 pg_autovacuum make error |