- 31 May, 1999 1 commit
- 
- 
Vadim B. Mikheev authored(no sense to hold it) or we'll be out of lock entries. Great thanks to Hiroshi Inoue. 
 
- 
- 30 May, 1999 4 commits
- 
- 
Tom Lane authored(Curious that gcc doesn't complain about this code...). 
- 
Tom Lane authoredis poor coding style. I agree. 
- 
Tom Lane authoredfile headers, to conform to established Postgres coding style and avoid warnings from gcc. 
- 
Tom Lane authoredafter checking for presence of C++ compiler. Odd we hadn't seen any reports of problems before... 
 
- 
- 29 May, 1999 7 commits
- 
- 
Tom Lane authoredwhen used with egcs --- now it does. 
- 
Vadim B. Mikheev authored2. Get rid of locking when updating statistics in vacuum. 3. Use QuerySnapshot in COPY TO and call SetQuerySnashot in main tcop loop before FETCH and COPY TO. 
- 
Vadim B. Mikheev authored
- 
Tom Lane authored
- 
Tom Lane authoredfew percent speedup in INSERT... 
- 
Tom Lane authoredredundant) SearchSysCache searches per table column in an INSERT, which accounted for a good percentage of the CPU time for INSERT ... VALUES(). Now it only does two searches in the typical case. 
- 
Tom Lane authoredcache access routines. 
 
- 
- 28 May, 1999 4 commits
- 
- 
Tom Lane authoredthrough MAXBACKENDS array entries used to be fine when MAXBACKENDS = 64. It's not so cool with MAXBACKENDS = 1024 (or more!), especially not in a frequently-used routine like SIDelExpiredDataEntries. Repair by making procState array size be the soft MaxBackends limit rather than the hard limit, and by converting SIGetProcStateLimit() to a macro. 
- 
Bruce Momjian authored
- 
Bruce Momjian authored
- 
Tom Lane authoreddo the right thing: look for a NOTICE message from the backend before we close our side of the socket. 6.4 libpq did not reliably print the backend's hara-kiri message, 'The Postmaster has informed me ...', because it only did the right thing if connection closure was detected during a read attempt instead of a write attempt. 
 
- 
- 27 May, 1999 13 commits
- 
- 
Bruce Momjian authorednew -x option to skip acl dump. 
- 
Thomas G. Lockhart authored
- 
Thomas G. Lockhart authored
- 
Thomas G. Lockhart authored
- 
Thomas G. Lockhart authoredUpdate for v6.5 release. 
- 
Thomas G. Lockhart authored
- 
Thomas G. Lockhart authored
- 
Thomas G. Lockhart authored
- 
Thomas G. Lockhart authored
- 
Bruce Momjian authored
- 
Bruce Momjian authored
- 
Bruce Momjian authoredbut the Makefile does break non g++. <<mak.patch>> Andreas 
- 
Bruce Momjian authored
 
- 
- 26 May, 1999 11 commits
- 
- 
Tom Lane authoredbefore any tuples are loaded, preserve the default '1000 tuples' table size estimate. 
- 
Tom Lane authoredthe backend does. Remove unnecessary limitation on field size in dumpClasses_dumpData (ie, -d or -D case). 
- 
Bruce Momjian authored
- 
Bruce Momjian authored
- 
Bruce Momjian authored
- 
Thomas G. Lockhart authoredAdd an appendix with more details on date/time attributes and handling. Update most references to Postgres version numbers to 6.5, *except* for the porting list which will require a report from a successful installation to be updated. 
- 
Thomas G. Lockhart authoredSome wording changes from Vadim's original text doc. Processes cleanly, but may need fixup. 
- 
Thomas G. Lockhart authoredNormalize markup for vacuumdb; content is the same. 
- 
Thomas G. Lockhart authoredpostgres-ref.sgml is not yet marked up. 
- 
Bruce Momjian authored
- 
Bruce Momjian authoredinserts. Change some variables to bool to be clearer. 
 
-