pgsql: Use our own getopt() and getopt_long() on Solaris, because that
This is a discussion on pgsql: Use our own getopt() and getopt_long() on Solaris, because that within the pgsql Committers forums, part of the PostgreSQL category; --> Log Message: ----------- Use our own getopt() and getopt_long() on Solaris, because that platform's versions don't handle long options ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-11-2008, 01:56 AM
| ||||
| ||||
 pgsql: Use our own getopt() and getopt_long() on Solaris, because that Log Message: ----------- Use our own getopt() and getopt_long() on Solaris, because that platform's versions don't handle long options the way we want. Per Zdenek Kotala. Tags: ---- REL8_0_STABLE Modified Files: -------------- pgsql: configure.in (r1.398.4.22 -> r1.398.4.23) (http://developer.postgresql.org/cvsw...&r2=1.398.4.23) configure (r1.424.4.21 -> r1.424.4.22) (http://developer.postgresql.org/cvsw...&r2=1.424.4.22) ---------------------------(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      |
 |
« pgsql: Avoid trying to print a NULL char pointer in --describe-config.
|
plscheme - plscheme: Avoid freeing SPI plan which will already be freed »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 04:59 AM.
