aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Modify wchar conversion routines to not fetch the next byte past the endTom Lane2001-03-08
| | | | | | | | | | | | | of a counted input string. Marinos Yannikos' recent crash report turns out to be due to applying pg_ascii2wchar_with_len to a TEXT object that is smack up against the end of memory. This is the second just-barely- reproducible bug report I have seen that traces to some bit of code fetching one more byte than it is allowed to. Let's be more careful out there, boys and girls. While at it, I changed the code to not risk a similar crash when there is a truncated multibyte character at the end of an input string. The output in this case might not be the most reasonable output possible; if anyone wants to improve it further, step right up...
* Repair a number of places that didn't bother to check whether PageAddItemTom Lane2001-03-07
| | | | | | | | | | succeeds or not. Revise rtree page split algorithm to take care about making a feasible split --- ie, will the incoming tuple actually fit? Failure to make a feasible split, combined with failure to notice the failure, account for Jim Stone's recent bug report. I suspect that hash and gist indices may have the same type of bug, but at least now we'll get error messages rather than silent failures if so. Also clean up rtree code to use Datum rather than char* where appropriate.
* > Applied. Thanks.Bruce Momjian2001-03-07
| | | | | | | | | | | One more :)) It's for improper function argumets for PLTCL_UNKNOWN_SUPPORT code I'm not an autoconf expert, but is it possible to enable unknown support in pltcl with configure option ? This support is really handy for real life usage of pl/tcl. seva@sevasoft.kiev.ua
* pltcl_loadmod has problems with big (>4k) modules because of missing incrBruce Momjian2001-03-07
| | | | | | in splitting code: seva@sevasoft.kiev.ua
* Believe $POSTGRES_LIB and $POSTGRES_INCLUDE only if they name actualTom Lane2001-03-06
| | | | directories, per suggestion from Robert Creager.
* Help message s/dump/restore/ (must have been copy&pasted from pg_dump).Peter Eisentraut2001-03-06
|
* Tue Mar 06 12:05:00 GMT 2001 peter@retep.org.ukPeter Mount2001-03-06
| | | | | - Removed org.postgresql.xa.Test from the JDBC EE driver as it's an old test class and prevented it from compiling.
* - Dump relevant parts of sequences only when doing schemaOnly & dataOnlyPhilip Warner2001-03-06
| | | | - Prevent double-dumping of sequences when dataOnly.
* - Only disable triggers in DataOnly (or implied data-only) restores.Philip Warner2001-03-06
| | | | - Change -U option to -L to allow -U to specify username in future. (pg_restore)
* Update email addresses.Bruce Momjian2001-03-05
|
* Here is the chinese_big5 patch for PgAccess. I've tested under ChineseBruce Momjian2001-03-05
| | | | | | | | Windows 2000 without any problem. Have fun. LM.Liu
* Ok, I've split todays commit into three, the first two already done had somePeter Mount2001-03-05
| | | | | | | | | | | | | | | | | | | | | bits in JDBC & the first set of tools into contrib. This is the third, and deals with enabling JDBC to be compiled with the main source. What it does is add a new option to configure: --with-java This option tells configure to look for ant (our build tool of choice) and if found, it then compiles both the JDBC driver and the new tools as part of the normal make. Also, when the postgresql install is done, all the .jar files are also installed into the ${PGLIB}/java directory (thought best to keep then separate) Now I had some conflicts when this applied so could someone please double check that everything is ok? Peter
* Minor fixes...Peter Mount2001-03-05
|
* Update mysql converter, new version released.Bruce Momjian2001-03-04
|
* Add configure check for -lunix, for QNX.Peter Eisentraut2001-03-03
| | | | | Recode test for equality of source and build directory using 'test -ef', because even using pwd you might not get equal strings. Thanks, QNX.
* Update the version number. We may change this to 7.1 if we align it withD'Arcy J.M. Cain2001-03-03
| | | | | | PostgreSQL. Add notice that development has moved into the PostgreSQL tree.
* Add oid to list of keys cached.D'Arcy J.M. Cain2001-03-03
| | | | Add a test to avoid an exception in certain cases.
* Incrementing version number in preparation for next release. Note that ID'Arcy J.M. Cain2001-03-03
| | | | | | | | | | | | | | | am talking with Thomas Lockhart about the idea of bringing the PyGreSQL version number into alignment with PostgreSQL so this may change to 7.1 before the release. I have added to the copyright to indicate that from now on the PostgreSQL copyright will apply. If someone wants to make that clearer please do. The existing copyrights need to stay there for now but if necessary I can ask Pascal Andre if he agrees to a different wording. Added reference to the Python DB-API 2.0 compliant API wrapper. Added reference to the PyGreSQL mailing list.
* Added postgres.h header for more type checking.D'Arcy J.M. Cain2001-03-03
| | | | | Changed the way that OID is retrieved on inserts. PQoidStatus appears to be deprecated so I am using PQoidValue instead.
* Add missing include.Peter Eisentraut2001-03-01
|
* Fix memory leak.Peter Eisentraut2001-03-01
|
* Ensure previous setting of pset.queryFout is restored after a failedTom Lane2001-03-01
| | | | backslash-g command.
* Add missing semicolon required by QNX shell.Peter Eisentraut2001-03-01
| | | | from "Tegge, Bernd" <tegge@repas-aeg.de>
* Remove HAVE_OPTARG per discussion in hackers list.Tatsuo Ishii2001-03-01
|
* Do not strip whitespace within quotes.Peter Eisentraut2001-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.
* 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.
* 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.
* 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).
* 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 comments on locks.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 ...
* 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>
* 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.
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-29 19:52:42 +0000