aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
* RemoveFunction didn't defend against too many args.Tom Lane2000-01-12
|
* Defend against > INDEX_MAX_KEYS keys in an index.Tom Lane2000-01-12
|
* CommentProc was careless about too many arguments.Tom Lane2000-01-12
|
* Put back erroneously removed zeroing of sentinel elementsTom Lane2000-01-12
| | | | in indexkeys, classlist arrays.
* Another FUNC_MAX_ARGS tweak.Tom Lane2000-01-11
|
* Wrong boundary condition on number-of-args check.Tom Lane2000-01-11
|
* Use symbolic INDEX_MAX_KEYS in pg_type entries for oidvectorTom Lane2000-01-11
| | | | and int2vector.
* Correct hardwired type information in bootstrap.Tom Lane2000-01-11
|
* More cleanups. Still doesn't work.Bruce Momjian2000-01-11
|
* More cleanups.Bruce Momjian2000-01-11
|
* More fixes, but still need +1 for FUNC_MAX_ARGSBruce Momjian2000-01-11
|
* Remove outdated comment about 8 arguments.Tom Lane2000-01-11
|
* Update type stuff.Bruce Momjian2000-01-10
|
* Cleanup for func args > 8.Bruce Momjian2000-01-10
|
* More updates for function call interface > 8.Bruce Momjian2000-01-10
|
* Update fmgr to allow 32 arguments.Bruce Momjian2000-01-10
|
* Make number of args to a function configurable.Bruce Momjian2000-01-10
|
* Rename oid8 -> oidvector and int28 -> int2vector. Cleanup of *out functions.Bruce Momjian2000-01-10
|
* Update int28out and out8out and _in_ functions to handle trailing zerosBruce Momjian2000-01-10
| | | | properly.
* Improve cache invalidation handling. EespeciallyHiroshi Inoue2000-01-10
| | | | | | this would fix TODO * elog() flushes cache, try invalidating just entries from current xact, perhaps using invalidation cache
* Fix oid8in and int28in for spacesBruce Momjian2000-01-10
|
* Move fixes for >8 indexed fields.Bruce Momjian2000-01-10
|
* Move INDEX_MAX_KEYS to postgres.h, and make it configurable for users.Bruce Momjian2000-01-10
|
* Repair subtle VACUUM bug that led to 'HEAP_MOVED_IN was not expected'Tom Lane2000-01-10
| | | | | | | | | | | | | | | | | | errors. VACUUM normally compacts the table back-to-front, and stops as soon as it gets to a page that it has moved some tuples onto. (This logic doesn't make for a complete packing of the table, but it should be pretty close.) But the way it was checking whether it had got to a page with some moved-in tuples was to look at whether the current page was the same as the last page of the list of pages that have enough free space to be move-in targets. And there was other code that would remove pages from that list once they got full. There was a kluge that prevented the last list entry from being removed, but it didn't get the job done. Fixed by keeping a separate variable that contains the largest block number into which a tuple has been moved. There's no longer any need to protect the last element of the fraged_pages list. Also, fix NOTICE messages to describe elapsed user/system CPU time correctly.
* Do not start if postmaster is running.Tatsuo Ishii2000-01-09
|
* Move SetPidFile() and firends to utils/init/miscinit.c fromTatsuo Ishii2000-01-09
| | | | | | postmaster/postmaster.c so that tcop/postgres.c can use them. Now we have an interlock between postmaster and postgres.
* Move SetPidFile() and firends to utils/init/miscinit.c so thatTatsuo Ishii2000-01-09
| | | | | tcop/postgres.c can use them. Now we have an interlock between postmaster and postgres.
* Another round of planner/optimizer work. This is just restructuring andTom Lane2000-01-09
| | | | | code cleanup; no major improvements yet. However, EXPLAIN does produce more intuitive outputs for nested loops with indexscans now...
* Need defense against oversize index entries in btree CREATE INDEX,Tom Lane2000-01-08
| | | | as well as when inserting entries into an existing index.
* Sorry, that I send this letter/patch again, but previous sending isBruce Momjian2000-01-07
| | | | | | | | | still without answer. I want continue with to_char(), but I need any answer for this patch. Please. Thank! (and sorry of my impatient :-) Karel
* Correct grammatical errorTatsuo Ishii2000-01-07
|
* Changed "triggered data change violation" detection codeJan Wieck2000-01-06
| | | | | | in trigger manager. Jan
* Fixed bug in targetlist expression replacement ofJan Wieck2000-01-06
| | | | | | SET DEFAULT referential action triggers. Jan
* Fix it's and its to be correct.Bruce Momjian2000-01-05
|
* Repair two recently reported problems:Thomas G. Lockhart2000-01-04
| | | | | | | | | | | | | | | | 1) datetime_pl_span() added the seconds field before adding the months field. This lead to erroneous results for e.g. select datetime '1999-11-30' + timespan '1 mon - 1 sec'; Reverse the order of operations to add months first. 2) tm2timespan() did all intermediate math as integer, converting to double at the very end. This resulted in hidden overflows when given very large integer days, hours, etc. For example, select '74565 days'::timespan; produced the wrong result. Change code to ensure that doubles are used for intermediate calculations. Thanks to Olivier PRENANT <ohp@pyrenet.fr> and Tulassay Zsolt <zsolt@tek.bke.hu> for problem reports and to Tom Lane for accurate analyses.
* Update DATEDEBUG removal.Bruce Momjian2000-01-02
|
* Remove DATEDEBUG because it didn't look Y2K safe, and fix timestamp elogBruce Momjian2000-01-02
| | | | to be Y2K safe.
* Generate double-sided LIKE indexquals that work even in weird locales,Tom Lane1999-12-31
| | | | | by continuing to increment the rightmost character until we get a string that is demonstrably greater than the pattern prefix.
* Clean up loose end in LIKE optimization fix: parser's code would generateTom Lane1999-12-31
| | | | | <= and >= indexquals from a LIKE even if the index in question didn't support those operators. (As, for example, a hash index does not.)
* Clean up datatypes and comments for op_class() routine.Tom Lane1999-12-31
|
* Revise init_sequence so that it doesn't leak memory if the requestedTom Lane1999-12-31
| | | | sequence doesn't exist.
* elog() was set up to call abort() if it saw an ERROR or FATAL exitTom Lane1999-12-30
| | | | | | | | | | during InitProcessingMode and the CurrentTransactionState was neither TRANS_DEFAULT nor TRANS_DISABLED. Unfortunately, after someone's recent change to start the transaction manager earlier in startup than it used to be started, that caused an abort() and consequent database system reset on quite harmless errors (such as rejecting an invalid user name!). As far as I can see, the test on CurrentTransactionState was completely useless anyway, so I've removed it.
* Repair bugs discussed in pghackers thread of 15 May 1999: creation of aTom Lane1999-12-30
| | | | | | relcache entry no longer leaks a small amount of memory. index_endscan now releases all the memory acquired by index_beginscan, so callers of it should NOT pfree the scan descriptor anymore.
* Improve subquery error message, now says "More than one tuple returnedBruce Momjian1999-12-29
| | | | by subselect used as expression."
* Update comment.Bruce Momjian1999-12-29
|
* Update comments.Bruce Momjian1999-12-29
|
* Removed LZTEXT datatype as discussed.Jan Wieck1999-12-28
| | | | Jan
* It turns out that the item size limit for btree indexes is about BLCKSZ/3,Tom Lane1999-12-26
| | | | | not BLCKSZ/2 as some of us thought. Add check for oversize item so that failure is detected before corrupting the index, not after.
* Clean up handling of explicit NULL constants. Cases likeTom Lane1999-12-24
| | | | | | | | | | | | | SELECT null::text; SELECT int4fac(null); work as expected now. In some cases a NULL must be surrounded by parentheses: SELECT 2 + null; fails SELECT 2 + (null); OK This is a grammatical ambiguity that seems difficult to avoid. Other than that, NULLs seem to behave about like you'd expect. The internal implementation is that NULL constants are typed as UNKNOWN (like untyped string constants) until the parser can deduce the right type.
* to live in a transaction before access to dbHiroshi Inoue1999-12-22
| | | | during backend startup.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 12:28:54 +0000