[PATCHES] minor compiler warning in backend/utils/adt/tsrank.c

while rebuilding postgres with msvc 2005 I noticed some minor compiler warnings: .\src\backend\utils\adt\tsrank.c(24): warning C4305: 'initializing' : truncation from 'double' to 'float' .\src\backend\utils\adt\tsrank.c(24): warning C4305: 'initializing' : truncation from 'double' to 'float' .

Re: [PATCHES] Implementation of aggregate functions

Thanks a lot to all of you for helping me on this issue. I will make sure that I post all my mails henceforth on the appropriate mailing list. Thanks once again for all the help, Best regards, Sayali Euler Taveira de Oliveira <[EMAIL PROTECTED]> wrote: sayali k wrote: > I am kee

Re: [PATCHES] Implementation of aggregate functions

sayali k wrote: > I am keen in implementing certain additional aggregate > functions like percentage, standard deviation etc. I > would like to know the complexity of this and also the > parts of the code which would have to be modified for > the same, > This is the wrong list to ask this kind of

Re: [PATCHES] minor compiler warning in backend/utils/adt/tsrank.c

Thank you, committed Hannes Eder wrote: while rebuilding postgres with msvc 2005 I noticed some minor compiler warnings: .\src\backend\utils\adt\tsrank.c(24): warning C4305: 'initializing' : truncation from 'double' to 'float' .\src\backend\utils\adt\tsrank.c(24): warning C4305: 'initializing

Re: [PATCHES] Various fixes for syslogger

ITAGAKI Takahiro wrote: Here are various fixes for syslogger. - syslogger_parseArgs_assert.patch (bug #3621) The assertion in syslogger_parseArgs() was wrong. The number of arguments passed to syslogger is changed to 4 in 8.1 or later. This patch should be appled to 8.1

Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded

"Marshall, Steve" <[EMAIL PROTECTED]> writes: > There is a problem in PL/TCL that can cause the postgres backend to > become multithreaded. Postgres is not designed to be multithreaded, so > this causes downstream errors in signal handling. We have seen this > cause a number of "unexpected st

[PATCHES] Patch to update log levels

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Here is a patch that documents the syslog log levels and their correlation to the PostgreSQL log levels per: http://archives.postgresql.org/pgsql-general/2007-09/msg00982.php Joshua D. Drake - -- === The PostgreSQL Company: Command P

Re: [PATCHES] [DOCS] Patch to update log levels

"Joshua D. Drake" <[EMAIL PROTECTED]> writes: > Here is a patch that documents the syslog log levels and their > correlation to the PostgreSQL log levels per: This seems like quite the wrong place to document it --- I'd have thought somewhere near the discussion of syslog logging would be appropri

Re: [PATCHES] Various fixes for syslogger

Andrew Dunstan <[EMAIL PROTECTED]> wrote: > > - syslogger_parseArgs_assert.patch (bug #3621) > > The assertion in syslogger_parseArgs() was wrong. The number of > > arguments passed to syslogger is changed to 4 in 8.1 or later. > > This patch should be appled to 8.1, 8.2 a

Re: [PATCHES] [DOCS] Patch to update log levels

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom Lane wrote: > "Joshua D. Drake" <[EMAIL PROTECTED]> writes: >> Here is a patch that documents the syslog log levels and their >> correlation to the PostgreSQL log levels per: > > This seems like quite the wrong place to document it --- I'd have >

[PATCHES] pgstats dead-space tracking

In the committed HOT patch, I removed pgstats tracking of dead space, because the system isn't doing anything with the info and it's not real clear that the info is of value to DBAs either. However, I did make a diff of the removal step; if we choose to put back the capability, the patch would be

Re: [PATCHES] adjust chr()/ascii() to prevent invalidly encoded data

Andrew Dunstan wrote: > > The attached patch is intended to ensure that chr() does not produce > invalidly encoded data, as recently discussed on -hackers. For UTF8, we > treat its argument as a Unicode code point; for all other multi-byte > encodings, we raise an error on any argument greater t

Re: [PATCHES] [DOCS] Patch to update log levels

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joshua D. Drake wrote: > Tom Lane wrote: >> "Joshua D. Drake" <[EMAIL PROTECTED]> writes: >>> Here is a patch that documents the syslog log levels and their >>> correlation to the PostgreSQL log levels per: >> This seems like quite the wrong place to d

Re: [PATCHES] adjust chr()/ascii() to prevent invalidly encoded data

Alvaro Herrera <[EMAIL PROTECTED]> writes: > Hmm, is this what we had agreed? I'm not sure I like it; if I'm using > chr() to produce characters, then the application is going to have to > worry about server_encoding in order to find the correct parameter to > pass to chr(). That's always been th