aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Tweak sorting so that nulls appear at the front of a descending sortTom Lane2001-06-02
| | | | | | | | | | | (vs. at the end of a normal sort). This ensures that explicit sorts yield the same ordering as a btree index scan. To be really sure that that equivalence holds, we use the btree entries in pg_amop to decide whether we are looking at a '<' or '>' operator. For a sort operator that has no btree association, we put the nulls at the front if the operator is named '>' ... pretty grotty, but it does the right thing in simple ASC and DESC cases, and at least there's no possibility of getting a different answer depending on the plan type chosen.
* Native Language Support (NLS)Peter Eisentraut2001-06-02
| | | | | | | | | | | Use --enable-nls to turn it on; see installation instructions for details. See developer's guide how to make use of it in programs and how to add translations. psql sources have been almost fully prepared and an incomplete German translation has been provided. In the backend, only elog() calls are currently translatable, and the provided German translation file is more of a placeholder.
* Paranoia about unordered comparisons in IEEE float math. If we areTom Lane2001-06-02
| | | | | | given values that compare as unordered, make sure we reply that they are equal, which is better than giving an arbitrary answer --- at least it doesn't depend on which one is passed as which arg.
* dllist.c is included in the frontend libpq interface via symlink.Jan Wieck2001-06-02
| | | | | | | There is no elog() available. Used fprintf(stderr, ...) and exit instead. Jan
* The following patch for JDBC fixes an issue with jdbc running on aBruce Momjian2001-06-01
| | | | | | | | non-multibyte database loosing 8bit characters. This patch will cause the jdbc driver to ignore the encoding reported by the database when multibyte isn't enabled and use the JVM default in that case. Barry Lind
* Check for malloc failure.Tom Lane2001-06-01
|
* Guard against malloc failure. Also, don't examine segP->lastBackendTom Lane2001-06-01
| | | | until we hold the spinlock.
* Check for malloc failure.Tom Lane2001-06-01
|
* If spi.c wants to use malloc, it better test for malloc failure.Tom Lane2001-06-01
|
* pltcl, plperl, and plpython all suffer the same bug previously fixedTom Lane2001-06-01
| | | | | | | | in plpgsql: they fail for datatypes that have old-style I/O functions due to caching FmgrInfo structs with wrong fn_mcxt lifetime. Although the plpython fix seems straightforward, I can't check it here since I don't have Python installed --- would someone check it?
* New improved version of bpcharin() may have got the truncation caseTom Lane2001-06-01
| | | | | | | | | right, but it failed to get the padding case right. This was obscured by subsequent application of bpchar() in all but one regression test case, and that one didn't fail in an obvious way --- trailing blanks are hard to see. Add another test case to make it more obvious if it breaks again.
* Fix for:Bruce Momjian2001-06-01
| | | | | | | | > Example form two pg_dump outputs > 7.1.2 : > COPY "list" FROM stdin; > 7.0.2 : > COPY "list" FROM stdin;
* Remove fastpath.c's lame attempt at caching function lookup info acrossTom Lane2001-06-01
| | | | | | | | | calls. This has never actually cached anything, because postgres.c does each fastpath call as a separate transaction command, and so fastpath.c would always decide that its cache was outdated. If it had worked, it would now be failing for calls of oldstyle functions due to dangling pointers in the FmgrInfo struct. Rip it out for simplicity and bug- proofing.
* - Synced preproc.y with gram.y.Michael Meskes2001-06-01
| | | | | | | - Synced pgc.l with scan.l. - Synced keyword.c. - Set ecpg version to 2.9.0. - Set library version to 3.3.0.
* Clean up some minor problems exposed by further thought about Panon's bugTom Lane2001-06-01
| | | | | | | | | | | | | | report on old-style functions invoked by RI triggers. We had a number of other places that were being sloppy about which memory context FmgrInfo subsidiary data will be allocated in. Turns out none of them actually cause a problem in 7.1, but this is for arcane reasons such as the fact that old-style triggers aren't supported anyway. To avoid getting burnt later, I've restructured the trigger support so that we don't keep trigger FmgrInfo structs in relcache memory. Some other related cleanups too: it's not really necessary to call fmgr_info at all while setting up the index support info in relcache entries, because those ScanKeyEntry structs are never used to invoke the functions. This should speed up relcache initialization a tiny bit.
* Update release 1.09 dateBruce Momjian2001-06-01
|
* Forgot SGML section section id tag for 7.1.Bruce Momjian2001-05-31
|
* Ooops, forgot to commit Makefile along with other changes.Tom Lane2001-05-31
|
* Support for emulating RTREE indexing in GiST. Contributed byTom Lane2001-05-31
| | | | Oleg Bartunov and Teodor Sigaev.
* Updates to make GIST work with multi-key indexes (from Oleg BartunovTom Lane2001-05-31
| | | | | and Teodor Sigaev). Declare key values as Datum where appropriate, rather than char* (Tom Lane).
* RI triggers would fail for datatypes using old-style equal function,Tom Lane2001-05-31
| | | | | | because cached fmgr info contained reference to a shorter-lived data structure. Also guard against possibility that fmgr_info could fail, leaving an incomplete entry present in the hash table.
* Allow IS and FOR in Pl/PgSQL cursors, per Oracle and ANSI. Jan-approved.Bruce Momjian2001-05-31
|
* Update TODO list.Bruce Momjian2001-05-31
|
* Update FAQ.Bruce Momjian2001-05-30
|
* Update FAQ.Bruce Momjian2001-05-30
|
* Oops, had 0.2 release date wrong.Bruce Momjian2001-05-30
|
* Remove OLD_FILE_NAMING code. No longer used.Bruce Momjian2001-05-30
|
* Update TODO list.Bruce Momjian2001-05-30
|
* Add recent UNDO/VACUUM thread to TODO.detail.Bruce Momjian2001-05-30
|
* Add "#define GIST_AM_OID".Tom Lane2001-05-30
|
* Tweak StrategyEvaluation data structure to eliminate hardwired limit onTom Lane2001-05-30
| | | | | number of strategies supported by an index AM. Add missing copyright notices and CVS $Header$ markers to GIST source files.
* Update TODO list.Bruce Momjian2001-05-30
|
* Remove unused, redundant header files.Tom Lane2001-05-30
|
* Fix broken $Header$ declaration.Tom Lane2001-05-30
|
* Properly compute max sys oid for 7.0 and 7.1.Bruce Momjian2001-05-30
|
* I just got bitten by this too. I use type timestamp in theBruce Momjian2001-05-30
| | | | | | | | | | | | | | | | | | | | | | database, and often need the latest timestamp, but want to format it as a date. With 7.0.x, I just select ts from foo order by ts desc limit 1 and in java: d = res.getDate(1); but this fails everywhere in my code now :( http://java.sun.com/j2se/1.3/docs/guide/jdbc/spec/jdbc-spec.frame7.html says The ResultSet.getXXX methods will attempt to convert whatever SQL type was returned by the database to whatever Java type is returned by the getXXX method. Palle Girgensohn
* Fix missing relation in FROM causing NOTICE. Cleanup.Bruce Momjian2001-05-30
|
* Remove reference to pg_class.relhaspkey from code. Column is unused.Bruce Momjian2001-05-30
|
* Mark as unused:Bruce Momjian2001-05-30
| | | | | | | | > Are these columns in pg_class: > relukeys | relfkeys | relhaspkey > unused or what? Christopher Kings
* Update TODO list.Bruce Momjian2001-05-30
|
* Remove SEP_CHAR from /contrib.Bruce Momjian2001-05-30
|
* Remove SEP_CHAR, replace with / or '/' as appropriate.Bruce Momjian2001-05-30
|
* Fix for Druid. We did not support some PROCEDURE queries.Bruce Momjian2001-05-30
| | | | Dave Cramer
* This is a docs patch to go with my DROP CONSTRAINT patch.Bruce Momjian2001-05-30
| | | | Christopher Kings
* These patches should fix check constraints not inheritingBruce Momjian2001-05-30
| | | | | | | | when added by alter table add constraint. The first file patches backend/commands/command.c and the latter is a patch to the alter table regression test. Stephan Szabo
* Playing with the earthdistance stuff, and found I needed the followingBruce Momjian2001-05-30
| | | | | | patch: Larry Rosenman
* Attached is my patch that adds DROP CONSTRAINT support to PostgreSQL. IBruce Momjian2001-05-30
| | | | | | | | | | | | | | | | | | | | basically want your guys feedback. I have sprinkled some of my q's thru the text delimited with the @@ symbol. It seems to work perfectly. [ Removed @@ comments because patch was reviewed. ] At the moment it does CHECK constraints only, with inheritance. However, due to the problem mentioned before with the mismatching between inherited constraints it may be wise to disable the inheritance feature for a while. it is written in an extensible fashion to support future dropping of other types of constraint, and is well documented. Please send me your comments, check my use of locking, updating of indices, use of ERROR and NOTICE, etc. and I will rework the patch based on feedback until everyone is happy with it... Christopher Kings
* Correct obsolete example of FROM-less query.Tom Lane2001-05-30
|
* In chapter:Bruce Momjian2001-05-30
| | | | | | | | | | | | | | | | | | | 7.7. Keys you have However, my application requires that each collection will also have a unique name. Why? So that a human being who wants to modify a collection will be able to identify it. It's much harder to know, if you have two collections named "Life Science", the the one tagged 24433 is the one you need, and the one tagged 29882 is not I think 'the the' shouldn't be repeated twice. Although taken from an email it would be cool to fix. Cheers, Maxim Maletsky
* Further conversions to Version 1 API. Also, fix boolean return to useD'Arcy J.M. Cain2001-05-30
| | | | PG_RETURN_BOOL(0) instead of return 0.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 16:09:29 +0000