- 22 6月, 2005 1 次提交
-
-
由 Neil Conway 提交于
is redundant after a check has already been made for "num < 0". The "set" variable can also be removed, as it is now no longer used. Per checking with Karel, this is the right fix. Per Coverity static analysis performed by EnterpriseDB.
-
- 15 6月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
"AT TIME ZONE", and not just the shorlist previously available. For example: SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London'; works fine now. It will also obey whatever DST rules were in effect at just that date, which the previous implementation did not. It also supports the AT TIME ZONE on the timetz datatype. The whole handling of DST is a bit bogus there, so I chose to make it use whatever DST rules are in effect at the time of executig the query. not sure if anybody is actuallyi *using* timetz though, it seems pretty unpredictable just because of this... Magnus Hagander
-
- 26 5月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
them, the executation behavior could be unexpected.
-
- 26 3月, 2005 2 次提交
- 13 1月, 2005 1 次提交
-
-
由 Tom Lane 提交于
of an sprintf() as a source string. Demonstrably does not work with recent gcc and/or glibc on some platforms.
-
- 01 1月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 20 11月, 2004 1 次提交
-
-
由 Tom Lane 提交于
-
- 01 11月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 29 10月, 2004 1 次提交
-
-
由 Tom Lane 提交于
Karel Zak
-
- 13 10月, 2004 1 次提交
-
-
由 Neil Conway 提交于
- remove another senseless "extern" keyword that was applied to a function definition - change a foo more function signatures from "some_type foo()" to "some_type foo(void)" - rewrite another K&R style function definition - make the type of the "action" function pointer in the KeyWord struct in src/backend/utils/adt/formatting.c more precise
-
- 30 8月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 29 8月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 21 5月, 2004 1 次提交
-
-
由 Tom Lane 提交于
and should do now that we control our own destiny for timezone handling, but this commit gets the bulk of the picayune diffs in place. Magnus Hagander and Tom Lane.
-
- 07 5月, 2004 1 次提交
-
-
由 Tom Lane 提交于
conversion of basic ASCII letters. Remove all uses of strcasecmp and strncasecmp in favor of new functions pg_strcasecmp and pg_strncasecmp; remove most but not all direct uses of toupper and tolower in favor of pg_toupper and pg_tolower. These functions use the same notions of case folding already developed for identifier case conversion. I left the straight locale-based folding in place for situations where we are just manipulating user data and not trying to match it to built-in strings --- for example, the SQL upper() function is still locale dependent. Perhaps this will prove not to be what's wanted, but at the moment we can initdb and pass regression tests in Turkish locale.
-
- 30 3月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
Fix to_char(year) for BC dates. Previously it returned one less than the current year. Add documentation mentioning that there is no 0 AD.
-
- 08 1月, 2004 1 次提交
-
-
由 Neil Conway 提交于
pointer type when it is not necessary to do so. For future reference, casting NULL to a pointer type is only necessary when (a) invoking a function AND either (b) the function has no prototype OR (c) the function is a varargs function.
-
- 25 12月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
> > needed, and other people in the past asked about it too. > > It is in Oracle, but you aren't exactly on the spot. It should be > > IYYY - 4 digits ('2003') > IYY - 3 digits ('003') > IY - 2 digits ('03') > I - 1 digit ('3') Here is an updated patch that does that. Kurt Roeckx
-
- 30 11月, 2003 1 次提交
-
-
由 PostgreSQL Daemon 提交于
$Header: -> $PostgreSQL Changes ...
-
- 29 9月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 03 9月, 2003 1 次提交
-
-
由 Tom Lane 提交于
From Karel Zak.
-
- 26 8月, 2003 1 次提交
-
-
由 Tom Lane 提交于
perform a timestamp-to-date coercion. Instead both routines share a subroutine that delivers the parsing result as a struct tm. This avoids problems with timezone dependency of to_date's result, and should be at least marginally faster too.
-
- 05 8月, 2003 1 次提交
-
-
由 Tom Lane 提交于
so it won't miss 'em again.
-
- 04 8月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 27 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
the bulk of the heavy lifting ...
-
- 02 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
(ye good olde uninitialized-local-variable).
-
- 28 3月, 2003 2 次提交
-
-
由 Bruce Momjian 提交于
block, ala C++.
-
由 Bruce Momjian 提交于
-
- 22 3月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 20 3月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
patch fix it -- but this patch doesn't contains tests or docs fixes. I will send it later. Fixed outputs: select to_char(x, '9999.999') as x, to_char(x, 'S9999.999') as s, to_char(x, 'SG9999.999') as sg, to_char(x, 'MI9999.999') as mi, to_char(x, 'PL9999.999') as pl, to_char(x, 'PLMI9999.999') as plmi, to_char(x, '9999.999SG') as sg2, to_char(x, '9999.999PL') as pl2, to_char(x, '9999.999MI') as mi2 from num; Karel Zak
-
- 11 3月, 2003 1 次提交
-
-
由 Tom Lane 提交于
PostgreSQL source code. Neil Conway
-
- 09 11月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
postgres.h or c.h includes a system header (such as stdio.h or stdlib.h), there's no need to specifically include it in any of the .c files in the backend. Neil Conway
-
- 20 9月, 2002 2 次提交
-
-
由 Bruce Momjian 提交于
* to_char(0,'FM999.99') returns a period, to_char(1,'FM999.99') does not Karel Zak
-
由 Bruce Momjian 提交于
fixes a few minor bugs (typos, potential buffer overruns, etc.), and fixes some spelling/grammar mistakes. Neil Conway
-
- 05 9月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 22 4月, 2002 1 次提交
-
-
由 Thomas G. Lockhart 提交于
Use "--enable-integer-datetimes" in configuration to use this rather than the original float8 storage. I would recommend the integer-based storage for any platform on which it is available. We perhaps should make this the default for the production release. Change timezone(timestamptz) results to return timestamp rather than a character string. Formerly, we didn't have a way to represent timestamps with an explicit time zone other than freezing the info into a string. Now, we can reasonably omit the explicit time zone from the result and return a timestamp with values appropriate for the specified time zone. Much cleaner, and if you need the time zone in the result you can put it into a character string pretty easily anyway. Allow fractional seconds in date/time types even for dates prior to 1BC. Limit timestamp data types to 6 decimal places of precision. Just right for a micro-second storage of int8 date/time types, and reduces the number of places ad-hoc rounding was occuring for the float8-based types. Use lookup tables for precision/rounding calculations for timestamp and interval types. Formerly used pow() to calculate the desired value but with a more limited range there is no reason to not type in a lookup table. Should be *much* better performance, though formerly there were some optimizations to help minimize the number of times pow() was called. Define a HAVE_INT64_TIMESTAMP variable. Based on the configure option "--enable-integer-datetimes" and the existing internal INT64_IS_BUSTED. Add explicit date/interval operators and functions for addition and subtraction. Formerly relied on implicit type promotion from date to timestamp with time zone. Change timezone conversion functions for the timetz type from "timetz()" to "timezone()". This is consistant with other time zone coersion functions for other types. Bump the catalog version to 200204201. Fix up regression tests to reflect changes in fractional seconds representation for date/times in BC eras. All regression tests pass on my Linux box.
-
- 03 4月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
and/or with GUC variables.
-
- 06 3月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
o Change all current CVS messages of NOTICE to WARNING. We were going to do this just before 7.3 beta but it has to be done now, as you will see below. o Change current INFO messages that should be controlled by client_min_messages to NOTICE. o Force remaining INFO messages, like from EXPLAIN, VACUUM VERBOSE, etc. to always go to the client. o Remove INFO from the client_min_messages options and add NOTICE. Seems we do need three non-ERROR elog levels to handle the various behaviors we need for these messages. Regression passed.
-
- 18 2月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
-