summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2000-01-15Add some examples to numeric regress test to verify that recently-fixedTom Lane
problems are indeed fixed.
2000-01-15Clean up problems with rounding/overflow code in NUMERIC, particularlyTom Lane
the case wherein zero was rejected for a field like NUMERIC(4,4). Miscellaneous other code beautification efforts.
2000-01-15Fix a passel of problems with incorrect calls to typinput and typoutputTom Lane
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().
2000-01-15Now that new psql is fflush()'ing properly, it emerges that severalTom Lane
regress test expected outputs were committed with NOTICEs appearing out of order. Update to correct results.
2000-01-15Update arrays regress test to reflect fact that several thingsTom Lane
work now that did not work in 6.5.
2000-01-15- Allow array on int8Peter Eisentraut
- Prevent permissions on indexes - Instituted --enable-multibyte option and tweaked the MB build process where necessary - initdb prompts for superuser password
2000-01-15Adapt to the changes of libpq(eliminateing using putenv()).Tatsuo Ishii
2000-01-15Eliminate using putenv().Tatsuo Ishii
2000-01-15Prepare for new psqlTatsuo Ishii
2000-01-15Fixed all elog related warnings, as well as a few others.Peter Eisentraut
2000-01-14Fixed psql variables vs array syntax, as well as minor psql enhancementsPeter Eisentraut
2000-01-14* User management commands no longer user pg_exec_query_dest -> more robustPeter Eisentraut
* 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.
2000-01-14Clean up some problems in new asynchronous-connection logicTom Lane
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.
2000-01-14Make PSQLexec's behavior on loss of connection more reasonable;Tom Lane
report original error before attempting reset, not after.
2000-01-14Make connection-failed messages a little friendlier onTom Lane
80-column displays...
2000-01-14Remove redundant and now-incorrect declaration of pstrdup.Tom Lane
2000-01-14Bump catversion to ensure initdb.Tom Lane
2000-01-14Revise quoting conventions in outfuncs/readfuncs so that nodeRead doesn'tTom Lane
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.
2000-01-13Fixed everything in and surrounding createdb and dropdb to make it morePeter Eisentraut
error-proof. Rearranged some old code and removed dead sections.
2000-01-13initdb didn't load pg_descriptionPeter Eisentraut
2000-01-13Add UDC (User Defined Characters) support to SJIS/EUC_JP conversionTatsuo Ishii
Update README so that it reflects all source file names Add an entry to make sjistest (testing between SJIS/EUC_JP conversion)
2000-01-12Fixed a few "fixes" and bugs. Adjusted messages and options to GNU suggestions.Peter Eisentraut
2000-01-12Multi-byte case fix by Oliver Elphick (olly@lfix.co.uk)Tatsuo Ishii
2000-01-12Use fmgr_array_args() to avoid dependency on FUNC_MAX_ARGS.Tom Lane
2000-01-12In PQfn(), defend against too many args, and avoid dependencyTom Lane
on FUNC_MAX_ARGS by using an appropriate fmgr() call.
2000-01-12RemoveFunction didn't defend against too many args.Tom Lane
2000-01-12Defend against > INDEX_MAX_KEYS keys in an index.Tom Lane
2000-01-12CommentProc was careless about too many arguments.Tom Lane
2000-01-12Put back erroneously removed zeroing of sentinel elementsTom Lane
in indexkeys, classlist arrays.
2000-01-11Make FUNC_MAX_ARGS equal INDEX_MAX_KEYS, as it should.Tom Lane
Set default INDEX_MAX_KEYS to 16. Document minimum safe value is 9.
2000-01-11oid8 => oidvector in alter_table regress testTom Lane
2000-01-11Another FUNC_MAX_ARGS tweak.Tom Lane
2000-01-11Wrong boundary condition on number-of-args check.Tom Lane
2000-01-11Ah-hah, there are attribute size constants lurking here too.Tom Lane
2000-01-11Use symbolic INDEX_MAX_KEYS in pg_type entries for oidvectorTom Lane
and int2vector.
2000-01-11Correct hardwired type information in bootstrap.Tom Lane
2000-01-11Remove no-longer-used symbols.Tom Lane
2000-01-11More cleanups. Still doesn't work.Bruce Momjian
2000-01-11More cleanups.Bruce Momjian
2000-01-11More fixes, but still need +1 for FUNC_MAX_ARGSBruce Momjian
2000-01-11Remove outdated comment about 8 arguments.Tom Lane
2000-01-10Fix initdb so it works, but still only for 8.Bruce Momjian
2000-01-10Update type stuff.Bruce Momjian
2000-01-10Cleanup for func args > 8.Bruce Momjian
2000-01-10More updates for function call interface > 8.Bruce Momjian
2000-01-10Update fmgr to allow 32 arguments.Bruce Momjian
2000-01-10Make number of args to a function configurable.Bruce Momjian
2000-01-10Rename oid8 -> oidvector and int28 -> int2vector. Cleanup of *out functions.Bruce Momjian
2000-01-10Update int28out and out8out and _in_ functions to handle trailing zerosBruce Momjian
properly.
2000-01-10Improve cache invalidation handling. EespeciallyHiroshi Inoue
this would fix TODO * elog() flushes cache, try invalidating just entries from current xact, perhaps using invalidation cache