aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Update TODO list.Bruce Momjian2001-02-28
|
* Update TODO list.Bruce Momjian2001-02-28
|
* Tweak portal (cursor) code so that it will not call the executor againTom Lane2001-02-27
| | | | | | | | | | | when user does another FETCH after reaching end of data, or another FETCH backwards after reaching start. This is needed because some plan nodes are not very robust about being called again after they've already returned NULL; for example, MergeJoin will crash in some states but not others. While the ideal approach would be for them all to handle this correctly, it seems foolish to assume that no such bugs would creep in again once cleaned up. Therefore, the most robust answer is to prevent the situation from arising at all.
* Mark new text<->date, text<->time, text<->timetz conversion functions asTom Lane2001-02-27
| | | | | | | | noncachable, so that CURRENT_DATE and CURRENT_TIME work as functions again, rather than being collapsed to constants immediately. Marking the reverse conversions noncachable might be overkill, but I'm not sure; do these datatypes have the notion of a CURRENT value? Better safe than sorry, for now.
* start of an admin tool for FreeBSD to help configure shared memory forMarc G. Fournier2001-02-27
| | | | | | | that machine I kept the name as generic as possible though, as other OS should have similar methods, so this can be extended "as appropriate" ...
* Massive commits for SunOS4 port.Tatsuo Ishii2001-02-27
|
* Fix vacuum analyze error.Tatsuo Ishii2001-02-27
| | | | | | | | | | | | | | | | | | vacuum analyze on pg_type fails if bogus entries remain in pg_operator. Here is a sample script to reproduce the problem. drop table t1; create table t1(i int); drop function foo(t1,t1); create function foo(t1,t1) returns bool as 'select true' language 'sql'; create operator = ( leftarg = t1, rightarg = t1, commutator = =, procedure = foo ); drop table t1; vacuum analyze;
* Fixed variable handling in preproc.y.Michael Meskes2001-02-26
|
* Allow pgaccess to input Japanese. See included mail.Tatsuo Ishii2001-02-26
| | | | | | | | | | | | | | | | | | | | | | | Subject: [HACKERS] pgaccess Japanese input capability patch From: Tatsuo Ishii <t-ishii@sra.co.jp> To: teo@flex.ro Cc: pgsql-hackers@postgresql.org, pgsql-interfaces@postgresql.org Date: Sat, 24 Feb 2001 21:41:14 +0900 Hi Teodorescu, I have made patches which enable pgaccess to input Japanese characters in the table editing window. As you might know, to input Japanese characters, we first type in "hiragana" then convert it to "kanji". To make this proccess transparent to tcl application programs, libraries are provided with localized version of Tcl/Tk. The patches bind certain keys to initiate a function (kanjiInput) that is responsible for the conversion process. If the function is not available, those keys will not be binded. Comments? -- Tatsuo Ishii
* Implement COMMIT_SIBLINGS parameter to allow pre-commit delay to occurTom Lane2001-02-26
| | | | | | | | | | | only if at least N other backends currently have open transactions. This is not a great deal of intelligence about whether a delay might be profitable ... but it beats no intelligence at all. Note that the default COMMIT_DELAY is still zero --- this new code does nothing unless that setting is changed. Also, mark ENABLEFSYNC as a system-wide setting. It's no longer safe to allow that to be set per-backend, since we may be relying on some other backend's fsync to have synced the WAL log.
* Even better example for operator precedence mis-parsing.Peter Eisentraut2001-02-25
|
* Doesn't need libpq.Peter Eisentraut2001-02-25
|
* Remove binary files.Peter Eisentraut2001-02-25
|
* At least on HPUX, select with delay.tv_sec = 0 and delay.tv_usec = 1000000Tom Lane2001-02-24
| | | | | | does not lead to a one-second delay, but to an immediate EINVAL failure. This causes CHECKPOINT to crash with s_lock_stuck much too quickly :-(. Fix by breaking down the requested wait div/mod 1e6.
* Choose a more suitable example for the operator precedence mis-parsingPeter Eisentraut2001-02-24
| | | | example.
* Markup, spell check, refine JDBC documentation.Peter Eisentraut2001-02-24
|
* When under postmaster, bogus arguments should cause proc_exit(0) notTom Lane2001-02-24
| | | | | proc_exit(1). Unless you think a system-wide restart is an appropriate response to bogus PGOPTIONS, that is.
* Fix pg_dump crashes caused by bogus use of va_start/va_end (only seenTom Lane2001-02-23
| | | | | on some platforms, which is not too surprising considering how platform specific these macros must be).
* I had a need to read such things as the backend locale and the catalogBruce Momjian2001-02-23
| | | | | | | | | | | | | | | | | | version number from the current database, and couldn't find any existing program to do that. linda:~$ pg_controldata Log file id: 0 Log file segment: 5 Last modified: Wed Feb 7 19:35:47 2001 Database block size: 8192 Blocks per segment of large relation: 131072 Catalog version number: 200101061 LC_COLLATE: en_GB LC_CTYPE: en_GB Log archive directory: Oliver Elphick Oliver.Elphick@lfix.co.uk
* As long as we're fixing this space calculation, let's actually do itTom Lane2001-02-23
| | | | | right. We should MAXALIGN the individual items because we'll allocate them individually, not as an array.
* Update TODO list.Bruce Momjian2001-02-23
|
* Update comments on locks.Bruce Momjian2001-02-23
|
* Update TODO list.Bruce Momjian2001-02-23
|
* Update TODO list.Bruce Momjian2001-02-23
|
* Bruce Momjian <pgman@candle.pha.pa.us> writes:Bruce Momjian2001-02-23
| | | | | | | | | | | > Is there one LOCKMETHODCTL for every backend? I thought there was only > one of them. >> >> You're right, that line is erroneous; it should read >> >> size += MAX_LOCK_METHODS * MAXALIGN(sizeof(LOCKMETHODCTL)); >> >> Not a significant error but it should be changed for clarity ...
* update to beta5 ... I think I ran cvs2cl right this time? :)Marc G. Fournier2001-02-23
|
* update to beta5Marc G. Fournier2001-02-23
|
* Resolve a compile error.Hiroshi Inoue2001-02-23
|
* Reindex of shared system indexes must be overwrite mode.Hiroshi Inoue2001-02-23
|
* Enhanced UTF-8/SJIS mapping generator, contributed byTatsuo Ishii2001-02-23
| | | | Eiji Tokuya" <e-tokuya@Mail.Sankyo-Unyu.co.jp>
* Freshen with a few recent platform reports:Thomas G. Lockhart2001-02-23
| | | | Linux/Alpha, Linux/Sparc, MacOS-X.
* chinese-gb -> chinese_gb.Bruce Momjian2001-02-23
|
* Rename to chinese-gbBruce Momjian2001-02-23
|
* More comment cleanups.Bruce Momjian2001-02-22
|
* More comment improvements.Bruce Momjian2001-02-22
|
* Clean up index/btree comments/macros, as approved.Bruce Momjian2001-02-22
|
* Change /*---- commants to /* where appropriate. pgindent will tightenBruce Momjian2001-02-22
| | | | up the comments later.
* Update flowchart xfig file.Bruce Momjian2001-02-22
|
* The attachement is the Chinese (GB) patch for PgAccess, don't knowBruce Momjian2001-02-22
| | | | | | | | | | | | | | if it's correct to post here. It's simple to do the translation, And I've test in 7.0.2 & current CVS, seems pretty good. If anyone want this little thing, I'll very happy. use it is very simple, just gunzip it and copy to $PGDIR/share/pgaccess/lib/languages/ for current CVS version, and $PGDIR/pgaccess/lib/languages/ for 7.0* BTW: I havn't got the tools to translate it to BIG5 encoding, is there anybody to to it? He Weiping(Laser Henry)
* Avoid 'FATAL: out of free buffers: time to abort !" errorHiroshi Inoue2001-02-22
| | | | during WAL recovery. Recovery failure is always serious.
* Adjust expected error message due to change of keyword case-folding.Tom Lane2001-02-22
|
* Add _REGEX_UTILS_H to avoid duplication.Tatsuo Ishii2001-02-22
|
* Update mutibyte docTatsuo Ishii2001-02-22
|
* Fix the bug report [ODBC] select from a table having more than 32 fields:Hiroshi Inoue2001-02-22
| | | | | reported by Matteo Cavalleri. Great thanks to Tom for his accurate analysis.
* Document timeofday(), mention start-of-transaction vs. current-timeTom Lane2001-02-21
| | | | semantics, a few other small improvements.
* Correct bogus output formatting of timeofday() function. A number ofTom Lane2001-02-21
| | | | microseconds < 100000 should be displayed as, eg, 13.000126, not 13.126.
* Comment improvements.Bruce Momjian2001-02-21
|
* Change case-folding of keywords to conform to SQL99 and fix misbehaviorTom Lane2001-02-21
| | | | | | | in Turkish locale. Keywords are now checked under pure ASCII case-folding rules ('A'-'Z'->'a'-'z' and nothing else). However, once a word is determined not to be a keyword, it will be case-folded under the current locale, same as before. See pghackers discussion 20-Feb-01.
* Fix markup. (A <keyword> isn't what it is in SQL.) Add jungle of morePeter Eisentraut2001-02-21
| | | | markup. ;-)
* Safe guard in case of imporper data is provided to elog()Tatsuo Ishii2001-02-21
| | | | in multi-byte build.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 20:43:18 +0000