- 29 9月, 2001 5 次提交
-
-
由 Thomas G. Lockhart 提交于
need more work, but at least they have something now.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 28 9月, 2001 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Thomas G. Lockhart 提交于
Start chapter on recovery techniques. Still needs work for release.
-
由 Thomas G. Lockhart 提交于
Define a new function, GetCurrentTransactionStartTimeUsec() to get the time to this precision. Allow now() and timestamp 'now' to use this higher precision result so we now have fractional seconds in this "constant". Add timestamp without time zone type. Move previous timestamp type to timestamp with time zone. Accept another ISO variant for date/time values: yyyy-mm-ddThh:mm:ss (note the "T" separating the day from hours information). Remove 'current' from date/time types; convert to 'now' in input. Separate time and timetz regression tests. Separate timestamp and timestamptz regression test.
-
由 Thomas G. Lockhart 提交于
Modify the timestamp test to reflect the "no time zone" behavior of this new code; timestamptz resembles the old timestamp code.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
more reasonable location for them.
-
由 Tom Lane 提交于
proposal of 26-Aug.
-
- 27 9月, 2001 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
Per gripe 9/26.
-
由 Tom Lane 提交于
check *can* return HEAPTUPLE_INSERT_IN_PROGRESS or HEAPTUPLE_DELETE_IN_PROGRESS, even though we have ShareLock on the relation. To wit, this can happen if the tuple was inserted/deleted by our own transaction. Per report from Justin Clift 9/23.
-
由 Tom Lane 提交于
need this, and it will create a Y2038 failure. Per report from David Wheeler, who is evidently running on a platform where time_t is already negative.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
supported platforms in pg_hba.conf.
-
- 26 9月, 2001 1 次提交
-
-
由 Michael Meskes 提交于
- Changed locale handling.
-
- 25 9月, 2001 2 次提交
-
-
由 Tatsuo Ishii 提交于
chars are in the input.
-
由 Peter Eisentraut 提交于
-
- 24 9月, 2001 2 次提交
-
-
由 Hiroshi Inoue 提交于
2) Change *Common* --> *Default*.
-
由 Peter Eisentraut 提交于
-
- 23 9月, 2001 16 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
handles this. Don't install our own odbcinst.ini. That's the driver manager's business.
-
由 Tatsuo Ishii 提交于
-
由 Tatsuo Ishii 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Changes: 1. Added support for boolean queries (indexable operator @@, looks like a @@ '1|(2&3)' 2. Some code cleanup and optimization Regards, Oleg
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
salt generation code. He also urged using better random source and making possible to choose using bcrypt and xdes rounds more easily. So, here's patch: * For all salt generation, use Solar Designer's own code. This is mostly due fact that his code is more fit for get_random_bytes() style interface. * New function: gen_salt(type, rounds). This lets specify iteration count for algorithm. * random.c: px_get_random_bytes() function. Supported randomness soure: /dev/urandom, OpenSSL PRNG, libc random() Default: /dev/urandom. * Draft description of C API for pgcrypto functions. New files: API, crypt-gensalt.c, random.c Marko Kreen
-
由 Bruce Momjian 提交于
summary of changes: . removal of the tablename property from build.xml . addition of a dropTable method in JDBC2Tests and cleanups of many methods in the same . all tests now use non-deprecated assertXYZ methods instead of the deprecated assert method . failure in TimestampTest (testSetTimestamp) fixed. The failure is because testSetTimestamp was inserting a timestamp with hour 7 but checkTimeTest was expecting a timestamp with hour 8. AFAICS, there are no issues wrt daylight savings time and timestamps being pushed in and pulled out (but more explicit tests should be added in the future) . failure in TimeTest (testGetTime) fixed. Times to be inserted were interpreted in the localtime zone but checking was done with the assumption that the insertion was done in GMT. . formatting changes in a few of the source files (because I found it convenient to have consistent formatting while working on them). The formatting is consistent with the new format for java source files in PostgreSQL. Liam Stewart
-