Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | - Allow array on int8 | Peter Eisentraut | 2000-01-15 |
| | | | | | | - Prevent permissions on indexes - Instituted --enable-multibyte option and tweaked the MB build process where necessary - initdb prompts for superuser password | ||
* | Adapt to the changes of libpq(eliminateing using putenv()). | Tatsuo Ishii | 2000-01-15 |
| | |||
* | Eliminate using putenv(). | Tatsuo Ishii | 2000-01-15 |
| | |||
* | Prepare for new psql | Tatsuo Ishii | 2000-01-15 |
| | |||
* | Fixed all elog related warnings, as well as a few others. | Peter Eisentraut | 2000-01-15 |
| | |||
* | Fixed psql variables vs array syntax, as well as minor psql enhancements | Peter Eisentraut | 2000-01-14 |
| | |||
* | * User management commands no longer user pg_exec_query_dest -> more robust | Peter Eisentraut | 2000-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. | ||
* | Clean up some problems in new asynchronous-connection logic | Tom Lane | 2000-01-14 |
| | | | | | | in libpq --- mostly, poor response to error conditions. You now actually get to see the postmaster's 'The Data Base System is starting up' message, which you didn't before. I suspect the SSL code is still broken though. | ||
* | Make PSQLexec's behavior on loss of connection more reasonable; | Tom Lane | 2000-01-14 |
| | | | | report original error before attempting reset, not after. | ||
* | Make connection-failed messages a little friendlier on | Tom Lane | 2000-01-14 |
| | | | | 80-column displays... | ||
* | Remove redundant and now-incorrect declaration of pstrdup. | Tom Lane | 2000-01-14 |
| | |||
* | Bump catversion to ensure initdb. | Tom Lane | 2000-01-14 |
| | |||
* | Revise quoting conventions in outfuncs/readfuncs so that nodeRead doesn't | Tom Lane | 2000-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 more | Peter Eisentraut | 2000-01-13 |
| | | | | error-proof. Rearranged some old code and removed dead sections. | ||
* | initdb didn't load pg_description | Peter Eisentraut | 2000-01-13 |
| | |||
* | Add UDC (User Defined Characters) support to SJIS/EUC_JP conversion | Tatsuo Ishii | 2000-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 Eisentraut | 2000-01-12 |
| | |||
* | Multi-byte case fix by Oliver Elphick (olly@lfix.co.uk) | Tatsuo Ishii | 2000-01-12 |
| | |||
* | Use fmgr_array_args() to avoid dependency on FUNC_MAX_ARGS. | Tom Lane | 2000-01-12 |
| | |||
* | In PQfn(), defend against too many args, and avoid dependency | Tom Lane | 2000-01-12 |
| | | | | on FUNC_MAX_ARGS by using an appropriate fmgr() call. | ||
* | RemoveFunction didn't defend against too many args. | Tom Lane | 2000-01-12 |
| | |||
* | Defend against > INDEX_MAX_KEYS keys in an index. | Tom Lane | 2000-01-12 |
| | |||
* | CommentProc was careless about too many arguments. | Tom Lane | 2000-01-12 |
| | |||
* | Put back erroneously removed zeroing of sentinel elements | Tom Lane | 2000-01-12 |
| | | | | in indexkeys, classlist arrays. | ||
* | Make FUNC_MAX_ARGS equal INDEX_MAX_KEYS, as it should. | Tom Lane | 2000-01-11 |
| | | | | Set default INDEX_MAX_KEYS to 16. Document minimum safe value is 9. | ||
* | oid8 => oidvector in alter_table regress test | Tom Lane | 2000-01-11 |
| | |||
* | Another FUNC_MAX_ARGS tweak. | Tom Lane | 2000-01-11 |
| | |||
* | Wrong boundary condition on number-of-args check. | Tom Lane | 2000-01-11 |
| | |||
* | Ah-hah, there are attribute size constants lurking here too. | Tom Lane | 2000-01-11 |
| | |||
* | Use symbolic INDEX_MAX_KEYS in pg_type entries for oidvector | Tom Lane | 2000-01-11 |
| | | | | and int2vector. | ||
* | Correct hardwired type information in bootstrap. | Tom Lane | 2000-01-11 |
| | |||
* | Remove no-longer-used symbols. | Tom Lane | 2000-01-11 |
| | |||
* | More cleanups. Still doesn't work. | Bruce Momjian | 2000-01-11 |
| | |||
* | More cleanups. | Bruce Momjian | 2000-01-11 |
| | |||
* | More fixes, but still need +1 for FUNC_MAX_ARGS | Bruce Momjian | 2000-01-11 |
| | |||
* | Remove outdated comment about 8 arguments. | Tom Lane | 2000-01-11 |
| | |||
* | Fix initdb so it works, but still only for 8. | Bruce Momjian | 2000-01-10 |
| | |||
* | Update type stuff. | Bruce Momjian | 2000-01-10 |
| | |||
* | Cleanup for func args > 8. | Bruce Momjian | 2000-01-10 |
| | |||
* | More updates for function call interface > 8. | Bruce Momjian | 2000-01-10 |
| | |||
* | Update fmgr to allow 32 arguments. | Bruce Momjian | 2000-01-10 |
| | |||
* | Make number of args to a function configurable. | Bruce Momjian | 2000-01-10 |
| | |||
* | Rename oid8 -> oidvector and int28 -> int2vector. Cleanup of *out functions. | Bruce Momjian | 2000-01-10 |
| | |||
* | Update int28out and out8out and _in_ functions to handle trailing zeros | Bruce Momjian | 2000-01-10 |
| | | | | properly. | ||
* | Improve cache invalidation handling. Eespecially | Hiroshi Inoue | 2000-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 spaces | Bruce Momjian | 2000-01-10 |
| | |||
* | Move fixes for >8 indexed fields. | Bruce Momjian | 2000-01-10 |
| | |||
* | Move INDEX_MAX_KEYS to postgres.h, and make it configurable for users. | Bruce Momjian | 2000-01-10 |
| | |||
* | Repair subtle VACUUM bug that led to 'HEAP_MOVED_IN was not expected' | Tom Lane | 2000-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 be | Tom Lane | 2000-01-09 |
| | | | | specified by regular-expression patterns. Add some more files. |