aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* More functions updated to new fmgr style --- money, name, tid datatypes.Tom Lane2000-08-03
| | | | | We're reaching the mopup stage here (good thing too, this is getting tedious).
* Repair bug noted by Paul Caskey: neqsel() has been generating a bogusTom Lane2000-08-03
| | | | | | | | | result, in fact nearly the opposite of what it should, because it was passing the not-equal operator to eqsel() which would use it to compare the value against the most common value in the column, and of course obtain the wrong result therefrom. Must pass the equality operator to eqsel() instead. Fortunately that's easy to get from the oprnegate link.
* Convert all remaining float4 and float8 functions to new fmgr style.Tom Lane2000-08-01
| | | | | | At this point I think it'd be possible to make float4 be pass-by-value without too much work --- and float8 too on machines where Datum is 8 bytes. Something to try when the mood strikes, anyway.
* - Added --create, --no-owner, --superuser, --no-reconnect (pg_dump & pg_restore)Philip Warner2000-08-01
| | | | | | | | | | | | - Added code to dump 'Create Schema' statement (pg_dump) - Don't bother to disable/enable triggers if we don't have a superuser (pg_restore) - Cleaned up code for reconnecting to database. - Force a reconnect as superuser before enabling/disabling triggers. - Added & Removed --throttle (pg_dump) - Fixed minor bug in language dumping code: expbuffres were not being reset. - Fixed version number initialization in _allocAH (pg_backup_archiver.c) - Added second connection when restoring BLOBs to allow temp. table to survive (db reconnection causes temp tables to be lost).
* Make acl-related functions safe for TOAST. Mark pg_class.relacl asTom Lane2000-07-31
| | | | | compressible but not externally storable (since we're not sure about whether creating a toast relation for pg_class would work).
* Cancel request while waiting for a lock should try to wakeHiroshi Inoue2000-07-31
| | | | up sleeping processes.
* Type lztext is toast.Tom Lane2000-07-30
| | | | | | | (Sorry, couldn't help it...) Removed type filename as well, since it's unused and probably useless. INITDB FORCED, because pg_rewrite columns are now plain text again.
* Convert all remaining geometric operators to new fmgr style. ThisTom Lane2000-07-30
| | | | | | | | allows fixing problems with operators that expected to be able to return a NULL, such as the '#' line-segment-intersection operator that tried to return NULL when the two segments don't intersect. (See, eg, bug report from 1-Nov-99 on pghackers.) Fix some other bugs in passing, such as backwards comparison in path_distance().
* PATH and POLYGON datatypes are now TOASTable. Associated functionsTom Lane2000-07-29
| | | | | updated to new fmgr style. Deleted hoary old functions for compatibility with pre-6.1 representations of these datatypes.
* bpchar, varchar, bytea, numeric are toastable --- if you initdb, whichTom Lane2000-07-29
| | | | | | I did not force. I marked numeric as compressable-but-not-move-off-able, partly to test that storage mode and partly because I've got doubts that numerics are large enough to need external storage.
* Fix acceptance of PATH as a type and column name.Thomas G. Lockhart2000-07-28
| | | | | | Note that this has changed some of the edge cases for what is accepted as a type name and/or column id. Regression test passes, but more tweaks may be coming...
* Add int2-vs-int8 comparison operators. These are now necessary becauseTom Lane2000-07-28
| | | | | | | the planner may try to generate them as a result of transitivity of the existing int2-vs-int4 and int4-vs-int8 operators. In fact, it is now necessary that mergejoinable cross-datatype operators form closed sets. Add an opr_sanity regress test to detect missing operators.
* Remove <values.h> inclusions, no-longer-needed MAXINT definitions.Tom Lane2000-07-28
|
* Fix sloppy macro coding (not enough parentheses).Tom Lane2000-07-28
|
* Make planner safe for recursive calls --- needed for cases whereTom Lane2000-07-27
| | | | eval_const_expressions tries to simplify an SQL function.
* Some pedantic compile syntax errors to fix with the following patchBruce Momjian2000-07-27
| | | | | | for today's snapshot Andreas
* Here is a bug and patch to fix it. I have tested this bug and fix onBruce Momjian2000-07-27
| | | | | | | | | | | | | | FreeBSD/Intel and DecUX/Alpha machines. The bug appears in postgresql 6.5.3 and 7.0.2. Can someone please review it and apply it to the source tree? Sometimes when the postgres connection dies it is necessary to attempt to reconnect. Calling the pgconnection::Connect method in a derived class leaks memory because it does not clear the current connection (if there is one). These patches ensures that any open connections are closed before attempting to open a new one. -Michael Richards
* Arrange to free planning memory (or most of it, anyway) at completionTom Lane2000-07-27
| | | | of planning. This should reduce memory requirements for large joins.
* Ensure that values stored within arrays are not toasted, perTom Lane2000-07-27
| | | | discussion on pghackers a few days ago.
* When dealing with OR-of-ANDs quals, extract multiple subclauses of an ANDTom Lane2000-07-26
| | | | | | to use with a multiple-key index. Formerly we would only extract clauses that had to do with the first key of the index, which was correct but didn't exploit the index fully.
* ExecRestrPos() really needs to raise ERROR, not a wimpy DEBUG message,Tom Lane2000-07-25
| | | | | if given a node type it doesn't support. As is, wrong results from a mergejoin would go undetected.
* Ensure that if the OID counter wraps around, we will not generate 0,Tom Lane2000-07-25
| | | | nor any OID in the reserved range (1-16383).
* Fix confusion between sizeof(long) and sizeof(long*), as well asTom Lane2000-07-25
| | | | | failure to MAXALIGN the start of shmem allocable space. No reports of trouble here, just compulsive tidiness.
* Add commentary about varying usage of scankeys in btree code.Tom Lane2000-07-25
|
* Clean up and document btree code for ordering keys. Neat stuff,Tom Lane2000-07-25
| | | | | | actually, but who could understand it with no comments? Fix bug while at it: _bt_orderkeys would try to invoke comparisons on NULL inputs, given the right sort of redundant quals.
* Update comments.Tom Lane2000-07-25
|
* Update bsdi templateBruce Momjian2000-07-24
|
* pg_backup_plain_text.c replaced by pg_backup_null.cPhilip Warner2000-07-24
|
* - no longer put ACLs at end of dumpPhilip Warner2000-07-24
| | | | | - connect as appropriate user in pg_restore with db connection - dump owner of rule in pg_dump
* Deduce equality constraints that are implied by transitivity ofTom Lane2000-07-24
| | | | | | | | mergejoinable qual clauses, and add them to the query quals. For example, WHERE a = b AND b = c will cause us to add AND a = c. This is necessary to ensure that it's safe to use these variables as interchangeable sort keys, which is something 7.0 knows how to do. Should provide a useful improvement in planning ability, too.
* Unset locale variables before running regression tests. (All of them!)Peter Eisentraut2000-07-23
| | | | Don't do config.status substitutions into the regression test makefile.
* Clean up some sloppy casts --- Oid vs. Datum, that sort of thing.Tom Lane2000-07-23
|
* Further cleanup of array behavior. Slice assignments to arrays withTom Lane2000-07-23
| | | | | | | | | | | varlena elements work now. Allow assignment to previously-nonexistent subscript position to extend array, but only for 1-D arrays and only if adjacent to existing positions (could do more if we had a way to represent nulls in arrays, but I don't want to tackle that now). Arrange for assignment of NULL to an array element in UPDATE to be a no-op, rather than setting the entire array to NULL as it used to. (Throwing an error would be a reasonable alternative, but it's never done that...) Update regress test accordingly.
* Shed some light onto SysV IPC configuration.Peter Eisentraut2000-07-22
|
* 2nd try for the index tuple toast hack. This time as suggestedJan Wieck2000-07-22
| | | | | | by Tom. Jan
* Make update lists like 'UPDATE tab SET foo[1] = bar, foo[3] = baz'Tom Lane2000-07-22
| | | | | | | | work as expected. THe underlying implementation is essentially 'SET foo = array_set(foo, 1, bar)', so we have to turn the items into nested invocations of array_set() to make it work correctly. Side effect: we now complain about 'UPDATE tab SET foo = bar, foo = baz' which is illegal per SQL92 but we didn't detect it before.
* Remove 'Array' node type, which has evidently been dead code forTom Lane2000-07-22
| | | | a very long time.
* Missed some array updates ...Tom Lane2000-07-22
|
* Arrays are toastable. (At least if you initdb, which I didn't force.)Tom Lane2000-07-22
| | | | | | | Remove a bunch of crufty code for large-object-based arrays, which is superseded by TOAST and likely hasn't worked in a long time anyway. Clean up array code a little, and in particular eliminate its habit of scribbling on the input array (ie, modifying the input tuple :-().
* maintainer-clean and distclean ought to remove dependency information as well.Peter Eisentraut2000-07-22
|
* Fix typo in version-mismatch error report.Tom Lane2000-07-21
|
* Further cleanup of btbuild (CREATE INDEX). Avoid storing unneededTom Lane2000-07-21
| | | | | | left keys during bottom-up index build, and leave some free space instead of packing the pages to the brim (so as to avoid vast numbers of page splits during the first interactive insertions).
* Fix sloppiness about alignment requirements in findsplitloc() spaceTom Lane2000-07-21
| | | | | calculation, also make it stop when it has a 'good enough' split instead of exhaustively trying all split points.
* - Support for TAR outputPhilip Warner2000-07-21
| | | | | | | - Support for BLOB output from pg_dump and input via pg_restore - Support for direct DB connection in pg_restore - Fixes in support for --insert flag - pg_dump now outputs in modified OID order
* - Support for BLOB output from pg_dump and input via pg_restorePhilip Warner2000-07-21
| | | | | | | - Support for direct DB connection in pg_restore - Fixes in support for --insert flag - pg_dump now outputs in modified OID order - various other bug fixes
* Need to switch to tuples memory context when replacing the toastedJan Wieck2000-07-21
| | | | | | one with the plain one. Jan
* Temporary fix to make TOAST vacuum-safe. All values are forced to beJan Wieck2000-07-21
| | | | | | | in memory (plain or compressed) in the tuple returned from the heap-am. So no index will ever contain an external reference. Jan
* Major overhaul of btree index code. Eliminate special BTP_CHAIN logic forTom Lane2000-07-21
| | | | | | | | | | | | duplicate keys by letting search go to the left rather than right when an equal key is seen at an upper tree level. Fix poor choice of page split point (leading to insertion failures) that was forced by chaining logic. Don't store leftmost key in non-leaf pages, since it's not necessary. Don't create root page until something is first stored in the index, so an unused index is now 8K not 16K. (Doesn't seem to be as easy to get rid of the metadata page, unfortunately.) Massive cleanup of unreadable code, fix poor, obsolete, and just plain wrong documentation and comments. See src/backend/access/nbtree/README for the gory details.
* Fixed DatabaseMetaData.getTableTypes()Peter Mount2000-07-20
|
* Fixed memory allocation problems when compressing multi-MBJan Wieck2000-07-20
| | | | | | | items. Lookup history is now a double linked list, used in a wrap-around style. Jan
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 05:31:54 +0000