aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* 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)
* Fixed a few "fixes" and bugs. Adjusted messages and options to GNU suggestions.Peter Eisentraut2000-01-12
|
* Multi-byte case fix by Oliver Elphick (olly@lfix.co.uk)Tatsuo Ishii2000-01-12
|
* 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.
* Make FUNC_MAX_ARGS equal INDEX_MAX_KEYS, as it should.Tom Lane2000-01-11
| | | | Set default INDEX_MAX_KEYS to 16. Document minimum safe value is 9.
* oid8 => oidvector in alter_table regress testTom Lane2000-01-11
|
* Another FUNC_MAX_ARGS tweak.Tom Lane2000-01-11
|
* Wrong boundary condition on number-of-args check.Tom Lane2000-01-11
|
* Ah-hah, there are attribute size constants lurking here too.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
|
* Remove no-longer-used symbols.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
|
* Fix initdb so it works, but still only for 8.Bruce Momjian2000-01-10
|
* 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.
* Update platform-specific-expected-file support so that platforms can beTom Lane2000-01-09
| | | | specified by regular-expression patterns. Add some more files.
* install_plpgsql is no longer a regress test (it's done via createlang);Tom Lane2000-01-09
| | | | remove the no-longer-used files.
* Add SetPidFile() and friends.Tatsuo Ishii2000-01-09
|
* 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.
* Add more portability to echo -n (code stolen from createlang)Tatsuo Ishii2000-01-09
| | | | Do not start postmaster if postgres is running
* New scheme for managing platform-specific regress test result files.Tom Lane2000-01-09
| | | | | | | Instead of hard-wiring one result file per platform, there is a map file 'resultmap' that says which one to use --- a lot like template/.similar. I have only created entries in resultmap for my own platform (HPUX) so far; feel free to add lines for other platforms.
* Remove obsolete platform-specific comparison files.Tom Lane2000-01-09
|
* First examples of multiplatform result comparison files.Tom Lane2000-01-09
|
* Remove obsolete platform-specific regress test comparison files.Tom Lane2000-01-09
| | | | | Note: don't put any of these back till you've grokked the new code for platform-specific comparisons that I'm about to commit...
* Remove CVS $Header lines from a couple of regress test files that hadTom Lane2000-01-09
| | | | | them --- it is just *way* too painful to keep expected results in sync when these are present.
* Update remaining tests for new psql, with the exception of 'arrays'.Tom Lane2000-01-09
|
* Update remaining tests for new psql, with the exception of 'arrays',Tom Lane2000-01-09
| | | | | | | which is broken in some weird way that I don't understand. I think it may be exposing a bug in the new psql --- for one thing, I get different results when I run psql by hand than the regress script gets. What the heck???
* Fix some missing substitutions of _OBJWD_ and _DLSUFFIX_.Tom Lane2000-01-09
|
* 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...
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 23:11:27 +0000