Re: [COMMITTERS] pgsql: Make directory name comparisons on Win32 case insensitive.

2009-04-04 Thread Magnus Hagander
Tom Lane wrote:
> m...@postgresql.org (Magnus Hagander) writes:
>> Log Message:
>> ---
>> Make directory name comparisons on Win32 case insensitive.
> 
> Hmm, for consistency you really should be doing
>   pg_tolower((unsigned char) *foo)
> here.
> 
> It's possible that the cast is not necessary on Windows, but
> even so code consistency is a good thing.

I see you've fixed this, thanks.

//Magnus


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[COMMITTERS] psqlodbc - psqlodbc: Improve the transactional control under

2009-04-04 Thread User Hinoue
Log Message:
---
Improve the transactional control under useDeclareFetch mode.

Modified Files:
--
psqlodbc:
connection.c (r1.178 -> r1.179)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/connection.c.diff?r1=1.178&r2=1.179)
connection.h (r1.91 -> r1.92)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/connection.h.diff?r1=1.91&r2=1.92)
convert.c (r1.177 -> r1.178)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/convert.c.diff?r1=1.177&r2=1.178)
execute.c (r1.93 -> r1.94)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/execute.c.diff?r1=1.93&r2=1.94)
options.c (r1.76 -> r1.77)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/options.c.diff?r1=1.76&r2=1.77)
pgapi30.c (r1.47 -> r1.48)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/pgapi30.c.diff?r1=1.47&r2=1.48)
psqlodbc.rc (r1.88 -> r1.89)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/psqlodbc.rc.diff?r1=1.88&r2=1.89)
qresult.c (r1.72 -> r1.73)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/qresult.c.diff?r1=1.72&r2=1.73)
results.c (r1.113 -> r1.114)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/results.c.diff?r1=1.113&r2=1.114)
statement.c (r1.140 -> r1.141)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/statement.c.diff?r1=1.140&r2=1.141)
version.h (r1.135 -> r1.136)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/version.h.diff?r1=1.135&r2=1.136)

-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[COMMITTERS] psqlodbc - psqlodbc: take some notes.

2009-04-04 Thread User H-saito
Log Message:
---
take some notes.

Modified Files:
--
psqlodbc/docs:
release.html (r1.48 -> r1.49)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/docs/release.html.diff?r1=1.48&r2=1.49)

-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[COMMITTERS] psqlodbc - psqlodbc: Fix an infinite loop in utf8_to_ucs2().

2009-04-04 Thread User Hinoue
Log Message:
---
Fix an infinite loop in utf8_to_ucs2().

Modified Files:
--
psqlodbc:
version.h (r1.136 -> r1.137)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/version.h.diff?r1=1.136&r2=1.137)
win_unicode.c (r1.22 -> r1.23)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/win_unicode.c.diff?r1=1.22&r2=1.23)

-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[COMMITTERS] pgsql: A session that does not have any live snapshots does not have to

2009-04-04 Thread Tom Lane
Log Message:
---
A session that does not have any live snapshots does not have to be waited for
when we are waiting for old snapshots to go away during a concurrent index
build.  In particular, this rule lets us avoid waiting for
idle-in-transaction sessions.

This logic could be improved further if we had some way to wake up when
the session we are currently waiting for goes idle-in-transaction.  However
that would be a significantly more complex/invasive patch, so it'll have to
wait for some other day.

Simon Riggs, with some improvements by Tom.

Modified Files:
--
pgsql/src/backend/commands:
indexcmds.c (r1.183 -> r1.184)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/indexcmds.c?r1=1.183&r2=1.184)
pgsql/src/backend/storage/ipc:
procarray.c (r1.48 -> r1.49)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/procarray.c?r1=1.48&r2=1.49)
pgsql/src/include/storage:
lock.h (r1.115 -> r1.116)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/lock.h?r1=1.115&r2=1.116)
procarray.h (r1.24 -> r1.25)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/procarray.h?r1=1.24&r2=1.25)

-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[COMMITTERS] pgsql: Remove the recently added node types ReloptElem and OptionDefElem

2009-04-04 Thread Tom Lane
Log Message:
---
Remove the recently added node types ReloptElem and OptionDefElem in favor
of adding optional namespace and action fields to DefElem.  Having three
node types that do essentially the same thing bloats the code and leads
to errors of confusion, such as in yesterday's bug report from Khee Chin.

Modified Files:
--
pgsql/src/backend/access/common:
reloptions.c (r1.25 -> r1.26)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/common/reloptions.c?r1=1.25&r2=1.26)
pgsql/src/backend/commands:
define.c (r1.103 -> r1.104)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/define.c?r1=1.103&r2=1.104)
foreigncmds.c (r1.6 -> r1.7)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/foreigncmds.c?r1=1.6&r2=1.7)
sequence.c (r1.158 -> r1.159)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/sequence.c?r1=1.158&r2=1.159)
typecmds.c (r1.132 -> r1.133)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/typecmds.c?r1=1.132&r2=1.133)
view.c (r1.114 -> r1.115)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/view.c?r1=1.114&r2=1.115)
pgsql/src/backend/nodes:
copyfuncs.c (r1.427 -> r1.428)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c?r1=1.427&r2=1.428)
equalfuncs.c (r1.350 -> r1.351)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/equalfuncs.c?r1=1.350&r2=1.351)
makefuncs.c (r1.63 -> r1.64)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/makefuncs.c?r1=1.63&r2=1.64)
outfuncs.c (r1.356 -> r1.357)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/outfuncs.c?r1=1.356&r2=1.357)
pgsql/src/backend/parser:
gram.y (r2.660 -> r2.661)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y?r1=2.660&r2=2.661)
parse_clause.c (r1.187 -> r1.188)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_clause.c?r1=1.187&r2=1.188)
pgsql/src/include/commands:
defrem.h (r1.93 -> r1.94)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/commands/defrem.h?r1=1.93&r2=1.94)
pgsql/src/include/foreign:
foreign.h (r1.3 -> r1.4)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/foreign/foreign.h?r1=1.3&r2=1.4)
pgsql/src/include/nodes:
makefuncs.h (r1.66 -> r1.67)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/makefuncs.h?r1=1.66&r2=1.67)
nodes.h (r1.221 -> r1.222)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/nodes.h?r1=1.221&r2=1.222)
parsenodes.h (r1.392 -> r1.393)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/parsenodes.h?r1=1.392&r2=1.393)

-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[COMMITTERS] pgsql: Make an attempt at fixing our current Solaris 11 breakage: add a

2009-04-04 Thread Tom Lane
Log Message:
---
Make an attempt at fixing our current Solaris 11 breakage: add a configure
probe for opterr (exactly like the one for optreset) and have getopt.c
define the variables only if configure doesn't find them in libc.

Modified Files:
--
pgsql:
configure (r1.634 -> r1.635)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/configure?r1=1.634&r2=1.635)
configure.in (r1.592 -> r1.593)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/configure.in?r1=1.592&r2=1.593)
pgsql/src/include:
pg_config.h.in (r1.138 -> r1.139)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/pg_config.h.in?r1=1.138&r2=1.139)
pgsql/src/port:
getopt.c (r1.11 -> r1.12)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/port/getopt.c?r1=1.11&r2=1.12)

-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[COMMITTERS] pgsql: Hmm, baiji thinks we need explicit 'extern' here.

2009-04-04 Thread Tom Lane
Log Message:
---
Hmm, baiji thinks we need explicit 'extern' here.

Modified Files:
--
pgsql/src/port:
getopt.c (r1.12 -> r1.13)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/port/getopt.c?r1=1.12&r2=1.13)

-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[COMMITTERS] pgsql: Remove contrib/intarray's definitions of the <@ and @> operators,

2009-04-04 Thread Tom Lane
Log Message:
---
Remove contrib/intarray's definitions of the <@ and @> operators, so that they
don't cause confusion with the built-in anyarray versions of those operators.
Adjust the module's index opclasses to support the built-in operators in place
of the private ones.

The private implementations are still available under their historical
names @ and ~, so no functionality is lost.  Some quick testing suggests
that they offer no real benefit over the core operators, however.

Per a complaint from Rusty Conover.

Modified Files:
--
pgsql/contrib/intarray:
_int.sql.in (r1.29 -> r1.30)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/intarray/_int.sql.in?r1=1.29&r2=1.30)
uninstall__int.sql (r1.10 -> r1.11)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/intarray/uninstall__int.sql?r1=1.10&r2=1.11)
pgsql/doc/src/sgml:
intarray.sgml (r1.6 -> r1.7)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/intarray.sgml?r1=1.6&r2=1.7)

-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[COMMITTERS] pgsql: I had always wondered why pg_config.h.win32 claimed that Windows

2009-04-04 Thread Tom Lane
Log Message:
---
I had always wondered why pg_config.h.win32 claimed that Windows
provides optreset.  Current mastodon results prove that in fact it
does not; it was only because getopt.c defined the variable anyway
that things failed to fall over.

Modified Files:
--
pgsql/src/include:
pg_config.h.win32 (r1.56 -> r1.57)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/pg_config.h.win32?r1=1.56&r2=1.57)

-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[COMMITTERS] pgsql: Remove a boatload of useless definitions of 'int optreset'.

2009-04-04 Thread Tom Lane
Log Message:
---
Remove a boatload of useless definitions of 'int optreset'.  If we
are using our own ports of getopt or getopt_long, those will define
the variable for themselves; and if not, we don't need these, because
we never touch the variable anyway.

Modified Files:
--
pgsql/src/backend/postmaster:
postmaster.c (r1.576 -> r1.577)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c?r1=1.576&r2=1.577)
pgsql/src/bin/initdb:
initdb.c (r1.169 -> r1.170)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/initdb/initdb.c?r1=1.169&r2=1.170)
pgsql/src/bin/pg_ctl:
pg_ctl.c (r1.109 -> r1.110)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_ctl/pg_ctl.c?r1=1.109&r2=1.110)
pgsql/src/bin/pg_dump:
pg_dump.c (r1.532 -> r1.533)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c?r1=1.532&r2=1.533)
pg_dumpall.c (r1.120 -> r1.121)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dumpall.c?r1=1.120&r2=1.121)
pg_restore.c (r1.96 -> r1.97)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_restore.c?r1=1.96&r2=1.97)
pgsql/src/bin/psql:
startup.c (r1.155 -> r1.156)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/startup.c?r1=1.155&r2=1.156)
pgsql/src/bin/scripts:
common.c (r1.35 -> r1.36)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/scripts/common.c?r1=1.35&r2=1.36)
common.h (r1.22 -> r1.23)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/scripts/common.h?r1=1.22&r2=1.23)
pgsql/src/include:
getopt_long.h (r1.10 -> r1.11)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/getopt_long.h?r1=1.10&r2=1.11)
pgsql/src/port:
getopt_long.c (r1.6 -> r1.7)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/port/getopt_long.c?r1=1.6&r2=1.7)

-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers