- 10 7月, 2001 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
postgresql.res.badint, since that's the name in the properties file.
-
- 08 7月, 2001 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
* NULLs are sorted differently in 7.2 * table correlation names are supported * GROUP BY, ORDER BY unrelated is supported since 6.4 * ESCAPE/LIKE only supported since 7.1 * outer joins only since 7.1 * preferred term for procedure is "function" * preferred term for catalog is "database" * supports SELECT for UPDATE since 6.5 * supports subqueries * supports UNION; supports UNION ALL since 7.1 * update some of the max lengths to match reality * rearrange some functions to match the order in the spec for easier maintenance
-
- 07 7月, 2001 9 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
redirections between the build files, which didn't work completely. Now you just go to the directory of your choice and run make. Clean up the build files to have a logical order, fix the unnecessary rebuilds, prevent the deleting targets from removing files they're not responsible for. Ant 1.3 does not have a bug. It deletes directories just fine if you follow the documentation.
-
由 Tom Lane 提交于
to wait until it's safe to remove tuples and compact free space in a shared buffer page. Miscellaneous small code cleanups in bufmgr, too.
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
the startup exchange is complete. Also make sure that packets defined as single bytes aren't sent with a trailing '\0'.
-
- 06 7月, 2001 4 次提交
-
-
由 Jan Wieck 提交于
Jan
-
由 Hiroshi Inoue 提交于
-
由 Tatsuo Ishii 提交于
-
由 Tom Lane 提交于
not holding a pin on the page. Use double instead of long to count rows in relation, so that code still works for > LONG_MAX rows in rel.
-
- 05 7月, 2001 3 次提交
-
-
由 Jan Wieck 提交于
Jan
-
由 Peter Eisentraut 提交于
Then, run a small reality test with $ANT to see whether it works.
-
由 Tom Lane 提交于
constraint. This case (a) is useless, (b) violates SQL92, and (c) is certain to cause a failure downstream when we try to create an index with duplicated column names. So give an appropriate error message instead of letting the index failure occur. Per report from Colin Strickland. NOTE: currently, CREATE INDEX fooi ON foo(f1,f1) still fails with 'cannot insert duplicate key' error. Should we change that too? What about functional indexes?
-
- 04 7月, 2001 9 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
misleading comments) from the PG_Stream class. Anders Bengtsson
-
由 Bruce Momjian 提交于
object inside the initialization section instead of doing it everytime the setTimestamp method is called. Thanks to Dave Harkness for this suggestion. Barry Lind
-
由 Bruce Momjian 提交于
the JDK 1.3 dependency. For a further explanation see my posting to the JDBC list on Friday, explaining why this is being done. Barry Lind
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
--verbose messages, which had not been considered so far. Output to the terminal should okay now; comments written into the dump are still English only, which may or may not be the desirable thing.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
to start it before we have acquired the data directory lock; also a bad idea to start it before we have set up to catch SIGCHLD signals.
-
由 Tom Lane 提交于
-
- 03 7月, 2001 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
useful as yet, since its primary source of information is (full) VACUUM, which makes a concerted effort to get rid of free space before telling the map about it ... next stop is concurrent VACUUM ...
-
由 Tom Lane 提交于
Probably the right fix is to remove 'current' special value entirely, but I don't want to see regression test failures until that happens.
-
由 Tom Lane 提交于
actually work. It had been throwing an Assert as of my recent changes to bufmgr.c, but was not really right even before that AFAICT.
-
- 01 7月, 2001 5 次提交
-
-
由 Tom Lane 提交于
immediately, we will fork a child even if the database state does not permit connections to be accepted (eg, we are in recovery mode). The child process will correctly reject the connection and exit as soon as it's finished collecting the connection request message. However, this means that reaper() must be prepared to see child process exit signals even while it's waiting for startup or shutdown process to finish. As was, a connection request arriving during a database recovery or shutdown would cause postmaster abort.
-
由 Peter Eisentraut 提交于
characteristics) to be set through GUC.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 D'Arcy J.M. Cain 提交于
I just finished changing the GENERIC files and the options(4) man page on NetBSD to make this clearer.
-