aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
* Included all yacc and lex files into the distribution.Peter Eisentraut2000-01-16
|
* Repair breakage of inherited constraint expressions --- needed aTom Lane2000-01-16
| | | | | | CommandCounterIncrement to make new relation visible before trying to parse/deparse the expressions. Also, eliminate unnecessary setheapoverride calls in AddNewAttributeTuples.
* Fix broken FOR UPDATE error message.Tom Lane2000-01-16
|
* Fix passing of atttypmod that Tom found.Bruce Momjian2000-01-16
|
* Clean up problems with rounding/overflow code in NUMERIC, particularlyTom Lane2000-01-15
| | | | | the case wherein zero was rejected for a field like NUMERIC(4,4). Miscellaneous other code beautification efforts.
* Fix a passel of problems with incorrect calls to typinput and typoutputTom Lane2000-01-15
| | | | | | | functions, which would lead to trouble with datatypes that paid attention to the typelem or typmod parameters to these functions. In particular, incorrect code in pg_aggregate.c explains the platform-specific failures that have been reported in NUMERIC avg().
* - Allow array on int8Peter Eisentraut2000-01-15
| | | | | | - Prevent permissions on indexes - Instituted --enable-multibyte option and tweaked the MB build process where necessary - initdb prompts for superuser password
* Fixed all elog related warnings, as well as a few others.Peter Eisentraut2000-01-15
|
* * User management commands no longer user pg_exec_query_dest -> more robustPeter Eisentraut2000-01-14
| | | | | | | | | | | | * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
* Revise quoting conventions in outfuncs/readfuncs so that nodeRead doesn'tTom Lane2000-01-14
| | | | | | choke on relation or attribute names containing spaces, quotes, or other special characters. This fixes a TODO item. It also forces initdb, since stored rule strings change.
* Fixed everything in and surrounding createdb and dropdb to make it morePeter Eisentraut2000-01-13
| | | | error-proof. Rearranged some old code and removed dead sections.
* Add UDC (User Defined Characters) support to SJIS/EUC_JP conversionTatsuo Ishii2000-01-13
| | | | | Update README so that it reflects all source file names Add an entry to make sjistest (testing between SJIS/EUC_JP conversion)
* Use fmgr_array_args() to avoid dependency on FUNC_MAX_ARGS.Tom Lane2000-01-12
|
* In PQfn(), defend against too many args, and avoid dependencyTom Lane2000-01-12
| | | | on FUNC_MAX_ARGS by using an appropriate fmgr() call.
* 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
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-07 09:02:51 +0000