summaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAgeFilesLines
* Add missing files from Karel, tip from Jan.Bruce Momjian2000-08-041-0/+159
|
* to_ascii( text )Bruce Momjian2000-08-041-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - encode 'text' from database encoding to ASCII to_ascii('\256\341k') to_ascii( text, int4 ) - encode 'text' from 'int4' encoding to ASCII to_ascii('\256\341k', 8) to_ascii( text, name ) - encode 'text' from 'name' encoding to ASCII to_ascii('\256\341k', 'LATIN2') Now is supported LATIN1, LATIN2, WIN1250. For other character sets I haven't good resources. Add new encoding is easy... If encoding is not supported returns ERROR. Note --- not exists total corect conversion to ASCII, this function try convert chars those is _probably_ interpret-able in ASCII for others use ' '. But for example for all Czech characters it is sufficient ... hmm Chinese / JAP and other complicated langs have bad luck here :-( Karel
* Subclasses inherit constraints of super classes properlyHiroshi Inoue2000-08-041-13/+84
|
* Fix tuptoaster bugs induced by making bytea toastable. Durn thing wasTom Lane2000-08-043-57/+63
| | | | | | | | | trying to toast tuples inserted into toast tables! Fix is two-pronged: first, ensure all columns of a toast table are marked attstorage='p', and second, alter the target chunk size so that it's less than the threshold for trying to toast a tuple. (Code tried to do that but the expression was wrong.) A few cosmetic cleanups in tuptoaster too. NOTE: initdb forced due to change in toaster chunk-size.
* Convert inet-related functions to new fmgr style. I have also taken itTom Lane2000-08-032-214/+204
| | | | | | | | on myself to do something about the non-self-consistency of the inet comparison functions. The results are probably still semantically wrong (inet and cidr should have different comparison semantics, I think) but at least the boolean operators now agree with each other and with the sort order of indexes on inet/cidr.
* Modify heap_open()/heap_openr() API per pghackers discussion of 11 July.Tom Lane2000-08-039-75/+104
| | | | | | | | | These two routines will now ALWAYS elog() on failure, whether you ask for a lock or not. If you really want to get a NULL return on failure, call the new routines heap_open_nofail()/heap_openr_nofail(). By my count there are only about three places that actually want that behavior. There were rather more than three places that were missing the check they needed to make under the old convention :-(.
* More functions updated to new fmgr style --- money, name, tid datatypes.Tom Lane2000-08-0315-244/+237
| | | | | 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-031-5/+58
| | | | | | | | | 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-017-940/+703
| | | | | | 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.
* Make acl-related functions safe for TOAST. Mark pg_class.relacl asTom Lane2000-07-313-135/+126
| | | | | 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-311-12/+14
| | | | up sleeping processes.
* Type lztext is toast.Tom Lane2000-07-307-508/+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-303-1191/+1367
| | | | | | | | 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-293-582/+365
| | | | | 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-296-628/+601
| | | | | | 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-281-34/+46
| | | | | | 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-281-2/+116
| | | | | | | 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-285-25/+6
|
* Make planner safe for recursive calls --- needed for cases whereTom Lane2000-07-273-54/+32
| | | | eval_const_expressions tries to simplify an SQL function.
* Some pedantic compile syntax errors to fix with the following patchBruce Momjian2000-07-271-2/+2
| | | | | | for today's snapshot Andreas
* Arrange to free planning memory (or most of it, anyway) at completionTom Lane2000-07-271-5/+50
| | | | of planning. This should reduce memory requirements for large joins.
* Ensure that values stored within arrays are not toasted, perTom Lane2000-07-271-6/+29
| | | | discussion on pghackers a few days ago.
* When dealing with OR-of-ANDs quals, extract multiple subclauses of an ANDTom Lane2000-07-261-26/+54
| | | | | | 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-251-11/+18
| | | | | 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-251-91/+83
| | | | nor any OID in the reserved range (1-16383).
* Fix confusion between sizeof(long) and sizeof(long*), as well asTom Lane2000-07-251-6/+7
| | | | | 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-251-1/+12
|
* Clean up and document btree code for ordering keys. Neat stuff,Tom Lane2000-07-252-178/+270
| | | | | | 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-251-4/+6
|
* Deduce equality constraints that are implied by transitivity ofTom Lane2000-07-244-156/+393
| | | | | | | | 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.
* Clean up some sloppy casts --- Oid vs. Datum, that sort of thing.Tom Lane2000-07-231-50/+28
|
* Further cleanup of array behavior. Slice assignments to arrays withTom Lane2000-07-232-228/+567
| | | | | | | | | | | 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-221-24/+56
|
* 2nd try for the index tuple toast hack. This time as suggestedJan Wieck2000-07-223-192/+79
| | | | | | by Tom. Jan
* Make update lists like 'UPDATE tab SET foo[1] = bar, foo[3] = baz'Tom Lane2000-07-221-49/+101
| | | | | | | | 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-224-119/+4
| | | | a very long time.
* Missed some array updates ...Tom Lane2000-07-221-7/+7
|
* Arrays are toastable. (At least if you initdb, which I didn't force.)Tom Lane2000-07-226-1587/+373
| | | | | | | 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 :-().
* Further cleanup of btbuild (CREATE INDEX). Avoid storing unneededTom Lane2000-07-212-138/+180
| | | | | | 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-212-38/+101
| | | | | calculation, also make it stop when it has a 'good enough' split instead of exhaustively trying all split points.
* Need to switch to tuples memory context when replacing the toastedJan Wieck2000-07-211-1/+9
| | | | | | one with the plain one. Jan
* Temporary fix to make TOAST vacuum-safe. All values are forced to beJan Wieck2000-07-212-6/+187
| | | | | | | 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-219-2764/+1533
| | | | | | | | | | | | 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 memory allocation problems when compressing multi-MBJan Wieck2000-07-201-28/+35
| | | | | | | items. Lookup history is now a double linked list, used in a wrap-around style. Jan
* Don't need this anymore. It's now handled in the Makefile.Peter Eisentraut2000-07-191-9/+0
|
* Add distprep target to take some of the job of the release_prep script.Peter Eisentraut2000-07-193-72/+64
| | | | | | | | | | | | | The latter updated accordingly. Also add `dist' and `distcheck' targets to play with, but caveat packager. Updated backend/bootstrap and backend/parser makefile to make them marginally builddir aware and fix the usual set of things. Add rule to automatically remake config.h dependent on config.h.in and config.status. (Adopted from Autoconf manual and about every other package.) On a good day we should now have a complete and accurate set of dependencies throughout everything.
* 'const' decorations are fine, but not when they're inserted withoutTom Lane2000-07-181-2/+2
| | | | bothering to clean up the resulting warnings ...
* Revise aggregate functions per earlier discussions in pghackers.Tom Lane2000-07-1726-1060/+1388
| | | | | | | | | | | There's now only one transition value and transition function. NULL handling in aggregates is a lot cleaner. Also, use Numeric accumulators instead of integer accumulators for sum/avg on integer datatypes --- this avoids overflow at the cost of being a little slower. Implement VARIANCE() and STDDEV() aggregates in the standard backend. Also, enable new LIKE selectivity estimators by default. Unrelated change, but as long as I had to force initdb anyway...
* Automatic dependency trackingPeter Eisentraut2000-07-161-4/+1
| | | | | The .DEFAULT rule in backend/Makefile is harmful -- removed. Replace `::' rules by `:'.
* This should be a slighly more complete patch for commands/command.cBruce Momjian2000-07-151-4/+188
| | | | | | | | | | | | | | | | | | | AlterTableAddConstraint. The major changes from the last patch are that it should hopefully check for references to temp tables (not in the shadow case, but at defination time) from permanent tables in foreign keys and refuse them and that it doesn't allow the table(s) being constrained to be views (because those cases don't currently work). Stephan SzaboThis should be a slighly more complete patch for commands/command.c AlterTableAddConstraint. The major changes from the last patch are that it should hopefully check for references to temp tables (not in the shadow case, but at defination time) from permanent tables in foreign keys and refuse them and that it doesn't allow the table(s) being constrained to be views (because those cases don't currently work). Stephan Szabo
View Lorry Controller Status