aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* I'm attaching those diffs for the Reference Guide in a tar file, asBruce Momjian2001-03-05
| | | | | | | | not all of them attached properly in the post I made a few minutes ago. Please disregard those earlier files. The diffs in the tar file replace them. Pierce Tyler
* 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
* Hmmm, a conflict with V1.104 of configure.in remained and broke configurePeter Mount2001-03-05
| | | | | | | (said redirection required when run). After checking using cvsweb, removed the offending conflict. Rebuilt configure using autoconf, and it now works fine.
* There's always 1 file missed out ;-)Peter Mount2001-03-05
| | | | Found while testing against a full checkout. Peter
* 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
|
* First batch of the tools merged in...Peter Mount2001-03-05
|
* PyGreSQL documentation. Based on the README, converted to DocBook byPeter Eisentraut2001-03-04
| | | | Mikhail Terekhov <terekhov@emc.com>.
* Update mysql converter, new version released.Bruce Momjian2001-03-04
|
* Document TEMP option.Tom Lane2001-03-03
|
* 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.
* Update TODO list.Bruce Momjian2001-03-02
|
* 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
|
* Update TODO list.Bruce Momjian2001-03-01
|
* Update TODO list.Bruce Momjian2001-03-01
|
* Do not strip whitespace within quotes.Peter Eisentraut2001-02-28
|
* 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 ...
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-31 02:56:18 +0000