This is a discussion on Re: pgsql: New versions of mingw have gettimeofday(), so add an autoconf within the pgsql Hackers forums, part of the PostgreSQL category; --> Magnus Hagander wrote: > Log Message: > ----------- > New versions of mingw have gettimeofday(), so add an autoconf ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Magnus Hagander wrote: > Log Message: > ----------- > New versions of mingw have gettimeofday(), so add an autoconf test > for this. > Can we backport this fix? I'm trying to setup a new windows build environment and this is currently halting my progress for back branches. Kris Jurka ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
| |||
| On Mon, 2007-11-19 at 02:50 -0700, Kris Jurka wrote: > Magnus Hagander wrote: > > Log Message: > > ----------- > > New versions of mingw have gettimeofday(), so add an autoconf test > > for this. > > > > Can we backport this fix? I'm trying to setup a new windows build > environment and this is currently halting my progress for back branches. Technically, it's fairly easy. And given that it's been working for a couple of betas of 8.3, it seems it should be safe. OTOH, the official build for 8.3 doesn't use it, so binary testers haven't seen it. But any issues should've been build issues rather than runtime ones, I think. So yeah, it would be reasonably easy to do, and probably a good idea. Anybody think we shouldn't? //Magnus ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| |||
| Magnus Hagander <magnus@hagander.net> writes: > On Mon, 2007-11-19 at 02:50 -0700, Kris Jurka wrote: >> Can we backport this fix? I'm trying to setup a new windows build >> environment and this is currently halting my progress for back branches. > Technically, it's fairly easy. And given that it's been working for a > couple of betas of 8.3, it seems it should be safe. OTOH, the official > build for 8.3 doesn't use it, so binary testers haven't seen it. But any > issues should've been build issues rather than runtime ones, I think. > So yeah, it would be reasonably easy to do, and probably a good idea. > Anybody think we shouldn't? Given that we're abandoning support for 8.0 and 8.1 on Windows, I'd say +1 for fixing 8.2, but not for any older branches. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |
| ||||
| On Wed, Nov 21, 2007 at 03:33:53PM -0500, Tom Lane wrote: > Magnus Hagander <magnus@hagander.net> writes: > > On Mon, 2007-11-19 at 02:50 -0700, Kris Jurka wrote: > >> Can we backport this fix? I'm trying to setup a new windows build > >> environment and this is currently halting my progress for back branches. > > > Technically, it's fairly easy. And given that it's been working for a > > couple of betas of 8.3, it seems it should be safe. OTOH, the official > > build for 8.3 doesn't use it, so binary testers haven't seen it. But any > > issues should've been build issues rather than runtime ones, I think. > > > So yeah, it would be reasonably easy to do, and probably a good idea. > > Anybody think we shouldn't? > > Given that we're abandoning support for 8.0 and 8.1 on Windows, > I'd say +1 for fixing 8.2, but not for any older branches. Done. //Magnus ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate |