[PATCHES] 8.0-NLS: czech

Hi, on URL: http://people.redhat.com/kzak/pg-nls-cs-21102004.patch.gz is new Czech translation of PostgreSQL messages. It's too big for e-mail attachment and mailing list limit. Thanks, Karel -- Karel Zak http://home.zf.jcu.cz/~zakkr ---(end of broadcast)--

[PATCHES] fix for Makefile.shlib multiply defined target

The attached patch fixes a problem with multiple target definitions that give rise to warnings like this: ../../src/Makefile.shlib:327: warning: overriding commands for target `libtsearch2.a' ../../src/Makefile.shlib:262: warning: ignoring old commands for target `libtsearch2.a' cheers andrew In

[PATCHES] fix windows contrib compile warnings for redefined macros

This patch fixes contrib so that it compiles under windows without warnings about redefines for min, max, V_UNKNOWN and IDIGNORE cheers andrew Index: intarray/_int.h === RCS file: /home/cvsmirror/pgsql/contrib/intarray/_int.h,v retri

Re: [PATCHES] fix windows contrib compile warnings for redefined macros

Andrew Dunstan <[EMAIL PROTECTED]> writes: > This patch fixes contrib so that it compiles under windows without > warnings about redefines for min, max, V_UNKNOWN and IDIGNORE Surely this is wrong. You might be able to assume that Windows' definitions for min/max are the same as what this code i

Re: [PATCHES] fix windows contrib compile warnings for redefined

Tom Lane wrote: Andrew Dunstan <[EMAIL PROTECTED]> writes: This patch fixes contrib so that it compiles under windows without warnings about redefines for min, max, V_UNKNOWN and IDIGNORE Surely this is wrong. You might be able to assume that Windows' definitions for min/max are the same

Re: [PATCHES] fix windows contrib compile warnings for redefined macros

Andrew Dunstan <[EMAIL PROTECTED]> writes: >> The right thing for the min/max macros is to get rid of them anyway, >> and use the Min/Max macros from c.h. > That's a fair point. I'll look at that. Actually I'm in the middle of doing that myself, so don't worry about it. r

Re: [PATCHES] fix windows contrib compile warnings for redefined

Andrew Dunstan <[EMAIL PROTECTED]> writes: > I didn't. In one case (IDIGNORE) I changed the name of the macro to > avoid the conflict, and in the other (V_UKNOWN) I removed the Windows > def which has no applicability in that context (the Windows version > comes from oleauto.h). Both of these c

[PATCHES] Example of function returning SETOF RECORD

Folks, Here's a patch that adds an example of using SETOF RECORD with the needed grammar. Cheers, D -- David Fetter [EMAIL PROTECTED] http://fetter.org/ phone: +1 510 893 6100 mobile: +1 415 235 3778 Remember to vote! ? setof_record.diff Index: doc/src/sgml/xfunc.sgml

Re: [PATCHES] Example of function returning SETOF RECORD

On Thu, Oct 21, 2004 at 09:26:39PM -0700, David Fetter wrote: > Folks, > > Here's a patch that adds an example of using SETOF RECORD with the > needed grammar. Oops. Please ignore previous patch. Here's the right one. Cheers, D -- David Fetter [EMAIL PROTECTED] http://fetter.org/ phone: +1 51

[PATCHES] hash_create(): check return code

hash_create() can return a NULL pointer if an error occurs (principally, when we're out of memory). Some of the call sites checked for this condition, but some did not. This patch fixes the remaining call sites to check the return value, and ereport(ERROR) if it is NULL. I'm not really sure whethe

[PATCHES] code cleanup in dynahash.c

This patch makes a minor code cleanup in dynahash.c: a function declared to return 'bool' only ever returned "true", so I changed it to return "void". I'll apply this to CVS before the end of the day, barring any objections. -Neil --- src/backend/utils/hash/dynahash.c +++ src/backend/utils/hash/

Re: [PATCHES] hash_create(): check return code

Neil Conway <[EMAIL PROTECTED]> writes: > I'm not really sure whether this is the correct fix, but it certainly > seems wrong to be doing the check in some places and not in others. > Another approach would be to elog(ERROR) when an error occurs in > hash_create(), which would be fine except there