aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Just noticed that use of 'volatile' in HPPA S_UNLOCK() was causing gccTom Lane2001-02-16
| | | | | to generate unnecessarily stupid code. Tweak macro to describe a series of store-constant ops, not store/load/store/load/store/load/store.
* Update README's install instructions to agree with current reality.Tom Lane2001-02-16
|
* Update bsdi shared memory stuff.Bruce Momjian2001-02-16
|
* Update BSDI FAQ.Bruce Momjian2001-02-16
|
* Defend against starting a non-MULTIBYTE-enabled backend in a databaseTom Lane2001-02-16
| | | | with encoding other than SQL_ASCII. Per recent discussion in pghackers.
* Some more updates...Peter Mount2001-02-16
| | | | | | | | | | | | | Fri Feb 17 15:11:00 GMT 2001 peter@retep.org.uk - Reduced the object overhead in PreparedStatement by reusing the same StringBuffer object throughout. Similarly SimpleDateStamp's are alse reused in a thread save manner. - Implemented in PreparedStatement: setNull(), setDate/Time/Timestamp using Calendar, setBlob(), setCharacterStream() - Clob's are now implemented in ResultSet & PreparedStatement! - Implemented a lot of DatabaseMetaData & ResultSetMetaData methods. We have about 18 unimplemented methods left in JDBC2 at the current time.
* Update BSDI SGML.Bruce Momjian2001-02-16
|
* ichar() has been renamed to chr(), so fix translation table.Tom Lane2001-02-16
|
* Fix bugs in pltcl's new return_null command: it was liable to go belly upTom Lane2001-02-16
| | | | | | | if the return datatype's input converter was at all strict, because the converter would get called on junk data when returning NULL. Also ensure that it gives an error rather than coredumping if someone tries to use it in a trigger function.
* Fix erroneous sort request in pltcl selftest.Tom Lane2001-02-16
|
* Clean up two rather nasty bugs in operator selection code.Tom Lane2001-02-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. If there is exactly one pg_operator entry of the right name and oprkind, oper() and related routines would return that entry whether its input type had anything to do with the request or not. This is just premature optimization: we shouldn't return the single candidate until after we verify that it really is a valid candidate, ie, is at least coercion-compatible with the given types. 2. oper() and related routines only promise a coercion-compatible result. Unfortunately, there were quite a few callers that assumed the returned operator is binary-compatible with the given datatype; they would proceed to call it without making any datatype coercions. These callers include sorting, grouping, aggregation, and VACUUM ANALYZE. In general I think it is appropriate for these callers to require an exact or binary-compatible match, so I've added a new routine compatible_oper() that only succeeds if it can find an operator that doesn't require any run-time conversions. Callers now call oper() or compatible_oper() depending on whether they are prepared to deal with type conversion or not. The upshot of these bugs is revealed by the following silliness in PL/Tcl's selftest: it creates an operator @< on int4, and then tries to use it to sort a char(N) column. The system would let it do that :-( (and evidently has done so since 6.3 :-( :-(). The result in this case was just a silly sort order, but the reverse combination would've provoked coredump from trying to dereference integers. With this fix you get more reasonable behavior: pltcl_test=# select * from T_pkey1 order by key1, key2 using @<; ERROR: Unable to identify an operator '@<' for types 'bpchar' and 'bpchar' You will have to retype this query using an explicit cast
* Add casting for numeric/float4/float8 type valueHiroshi Inoue2001-02-16
| | | | | | | | | | | automatically to compensate the lack of automatic conversion functionality of PostgreSQL server. For example if there's a numeric type binding 1.2567 --> 1.2567::numeric. I hope this change would enable the use of numeric type in MS-Access etc. Thanks Hiroki Kataoka for his checking my code.
* Update bsdi faq.Bruce Momjian2001-02-16
|
* Update bsdi faq.Bruce Momjian2001-02-16
|
* Take OUTER JOIN semantics into account when estimating the size of joinTom Lane2001-02-16
| | | | | relations. It's not very bright, but at least it now knows that A LEFT JOIN B must produce at least as many rows as are in A ...
* Update FAQ.Bruce Momjian2001-02-15
|
* Update FAQ.Bruce Momjian2001-02-15
|
* Add some notes about memory management of RI plans.Tom Lane2001-02-15
|
* Update comments about memory management.Tom Lane2001-02-15
|
* Update notes about memory context scheme.Tom Lane2001-02-15
|
* Update obsolete wording of error message.Tom Lane2001-02-15
|
* Although we can't support out-of-line TOAST storage in indexes (yet),Tom Lane2001-02-15
| | | | | | | | compressed storage works perfectly well. Might as well have a coherent strategy for applying it, rather than the haphazard store-what-you-get approach that was in the code before. The strategy I've set up here is to attempt compression of any compressible index value exceeding BLCKSZ/16, or about 500 bytes by default.
* Further polishing of documentation about new fmgr call convention.Tom Lane2001-02-15
|
* Reduce default selectivity estimates for geometric operators; it seemsTom Lane2001-02-15
| | | | | | | the old ones were not small enough to ensure r-tree and gist indexes would get picked when available. These numbers are totally bogus anyway, but in the absence of any real estimation technique, we'd like to select indexes when available ...
* Update a couple of obsolete comments.Tom Lane2001-02-15
|
* Update TODO list.Bruce Momjian2001-02-15
|
* Update TODO list.Bruce Momjian2001-02-15
|
* Update for Tatsuo.Bruce Momjian2001-02-15
|
* 1) Change transaction boundary in autocommit off modeHiroshi Inoue2001-02-15
| | | | | | | | | | per recent discussion in pgsql-odbc. Now SELECT is a boundary but VACUUM isn't. 2) Put back the error handling behavior. When elog(ERROR) was detected the driver automatically issue "ABORT" if a transaction is in progress. 3) Driver version is 7.01.0003(Dave already set it but it was put back).
* Clarify meaning of GEQO_THRESHOLD parameter.Tom Lane2001-02-15
|
* Improve documentation of JOIN syntax. Explain NATURAL as an alternativeTom Lane2001-02-15
| | | | | to ON and USING for specifying the join condition, not as an independent kind of join semantics.
* Unicode <-> SJIS new mapping tables (based on CP932.TXT) contributed byTatsuo Ishii2001-02-15
| | | | Eiji Tokuya" <e-tokuya@Mail.Sankyo-Unyu.co.jp>
* Arrange for ORDER BY an expression on a UNION/INTERSECT/EXCEPT result,Tom Lane2001-02-15
| | | | | | | | | | such as SELECT f1 FROM foo UNION SELECT ... ORDER BY upper(f1) to draw 'ORDER BY on a UNION/INTERSECT/EXCEPT result must be on one of the result columns' rather than the uninformative 'f1 not found' we were producing before. Eventually this should actually work, but that looks much too hard to try to implement in late beta...
* Repair problems with duplicate index names generated when CREATE TABLETom Lane2001-02-14
| | | | specifies redundant UNIQUE conditions.
* Change scoping of table and join refnames to conform to SQL92: a JOINTom Lane2001-02-14
| | | | | | | | | clause with an alias is a <subquery> and therefore hides table references appearing within it, according to the spec. This is the same as the preliminary patch I posted to pgsql-patches yesterday, plus some really grotty code in ruleutils.c to reverse-list a query tree with the correct alias name depending on context. I'd rather not have done that, but unless we want to force another initdb for 7.1, there's no other way for now.
* Alter documentation of boolean type, add example. Someone figured that itPeter Eisentraut2001-02-14
| | | | | | | wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
* Format <structname>, <structfield>, and <type> mono-spaced.Peter Eisentraut2001-02-14
|
* Web Feb 14 17:29:00 GMT 2001 peter@retep.org.ukPeter Mount2001-02-14
| | | | | | - Fixed bug in LargeObject & BlobOutputStream where the stream's output was not flushed when either the stream or the blob were closed. - Fixed PreparedStatement.setBinaryStream() where it ignored the length
* Update TODO list.Bruce Momjian2001-02-14
|
* Add 7.X to dialog box.Bruce Momjian2001-02-14
|
* Back out all ODBC formatting changes, and back out removal of <6.4Bruce Momjian2001-02-14
| | | | | | protocol. I have left in Tom's SOCK_get_next_byte() fix, and the new win32.mak file addition. I have also left in the 'X' connection close fix.
* Update TODO list.Bruce Momjian2001-02-14
|
* Hmm, so referencing a CSS stylesheet when there isn't one doesn't workPeter Eisentraut2001-02-13
| | | | everywhere.
* Fix markup.Peter Eisentraut2001-02-13
|
* Didn't work when Makefile.custom is missing.Peter Eisentraut2001-02-13
|
* Custom DSSSL stylesheet. Style changes included here:Peter Eisentraut2001-02-13
| | | | | | | | | | | | HTML: * make .html the default extension * allow use of CSS stylesheet ("stylesheet.css", not included) * make <set> TOC two levels deep * put time of creation into meta header Print: * make print output justified by default * footnotes at bottom of each page * allow TeX to hyphenate
* Fix tag.Peter Eisentraut2001-02-13
|
* Update TODO list.Bruce Momjian2001-02-13
|
* Update TODO list.Bruce Momjian2001-02-13
|
* Comments about GetFreeXLBuffer().Vadim B. Mikheev2001-02-13
| | | | | GetFreeXLBuffer(): use Insert->LgwrResult instead of private LgwrResult copy if it's more fresh (attempt to avoid acquiring info_lck/lgwr_lck).
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 07:52:35 +0000