summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
1999-05-30Clean up uninitialized-variable warning from egcs.Tom Lane
(Curious that gcc doesn't complain about this code...).
1999-05-30egcs thinks omitting the return type in a function declarationTom Lane
is poor coding style. I agree.
1999-05-30Replace static rcsid[] strings by IDENTIFICATION comments inTom Lane
file headers, to conform to established Postgres coding style and avoid warnings from gcc.
1999-05-30configure.in forgot to do AC_LANG_C to reselect C-based testsTom Lane
after checking for presence of C++ compiler. Odd we hadn't seen any reports of problems before...
1999-05-29Turns out that configure's test for HPUXMATHLIB didn't workTom Lane
when used with egcs --- now it does.
1999-05-291. Run all pg_dump queries in single serializable transaction.Vadim B. Mikheev
2. 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.
1999-05-29Fix xid table sizing.Vadim B. Mikheev
1999-05-29Missing semicolons in non-HAS_TEST_AND_SET code paths :-(Tom Lane
1999-05-29Avoid redundant SysCache searches in coerce_type, for anotherTom Lane
few percent speedup in INSERT...
1999-05-29new_relation_targetlist used to cause about 8 separate (andTom Lane
redundant) 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.
1999-05-29Clean up inefficient and just plain bad code in some hot-spotTom Lane
cache access routines.
1999-05-28Repair performance problem in SI segment manipulations: iteratingTom Lane
through 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.
1999-05-28Clean up mention of gmake vs. make.Bruce Momjian
1999-05-28Update pygresql version stamp.Bruce Momjian
1999-05-28When closure of the backend connection is detected during pqFlush,Tom Lane
do 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.
1999-05-27Make pg_dump dump ACL's by default, print warning on use of -z, and addBruce Momjian
new -x option to skip acl dump.
1999-05-27More info is in sgml and html docs so this is now obsolete.Thomas G. Lockhart
1999-05-27FAQs contributed for this release.Thomas G. Lockhart
1999-05-27Markup fixes.Thomas G. Lockhart
1999-05-27Markup fixes.Thomas G. Lockhart
Update for v6.5 release.
1999-05-27Significant updates from Vince Vielhaber.Thomas G. Lockhart
1999-05-27Remove disclaimer about exact numeric types. They work now!Thomas G. Lockhart
1999-05-27Refresh FreeBSD info.Thomas G. Lockhart
1999-05-27Significant update from Vince Vielhaber.Thomas G. Lockhart
1999-05-27Update release notes for 6.5.Bruce Momjian
1999-05-27Clean up release sgml file.Bruce Momjian
1999-05-27I am not sure if libpq++ will compile with non g++ compilers,Bruce Momjian
but the Makefile does break non g++. <<mak.patch>> Andreas
1999-05-27Fix for crypt memory leak, from James ThompsonBruce Momjian
1999-05-26Patch from Andreas: when CREATE TABLE is followed by CREATE INDEXTom Lane
before any tuples are loaded, preserve the default '1000 tuples' table size estimate.
1999-05-26Fix pg_dump to use the same maximum-query-size constant asTom Lane
the backend does. Remove unnecessary limitation on field size in dumpClasses_dumpData (ie, -d or -D case).
1999-05-26Fix compile of plpgsql by adding 'extern int yylineno.'Bruce Momjian
1999-05-26Display numeric precision on \d.Bruce Momjian
1999-05-26Allow GROUPs to be dumped properly.Bruce Momjian
1999-05-26Add chapters on CVS access, MVCC, SQL theory to the docs.Thomas G. Lockhart
Add 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.
1999-05-26Chapter on multi-version concurrency control from Vadim.Thomas G. Lockhart
Some wording changes from Vadim's original text doc. Processes cleanly, but may need fixup.
1999-05-26Add new reference pages for postmaster and postgres.Thomas G. Lockhart
Normalize markup for vacuumdb; content is the same.
1999-05-26First copy from the man pages.Thomas G. Lockhart
postgres-ref.sgml is not yet marked up.
1999-05-26Fix for NT from Horak DanielBruce Momjian
1999-05-26Disable use of -o and -d pg_dump options together. Can't set oids inBruce Momjian
inserts. Change some variables to bool to be clearer.
1999-05-26Add fix for 0x7fU constants to pgindentBruce Momjian
1999-05-26Allow pg_dump -v display proper table/sequence count display.Bruce Momjian
1999-05-26Make functions static or NOT_USED as appropriate.Bruce Momjian
1999-05-26Give BEOS a chance ...Marc G. Fournier
1999-05-25Another pgindent run. Sorry folks.Bruce Momjian
1999-05-25Make 0x007f -> (unsigned)0x7f to make pgindent happy.Bruce Momjian
1999-05-25Get rid of page-level locking in btree-s.Vadim B. Mikheev
BT_READ/BT_WRITE are BUFFER_LOCK_SHARE/BUFFER_LOCK_EXCLUSIVE now. Also get rid of #define BT_VERSION_1 - we use version 1 as default for near two years now.
1999-05-25Get rid of page-level locking in btree-s.Vadim B. Mikheev
LockBuffer is used to acquire read/write access to index pages. Pages are released before leaving index internals.
1999-05-25pgindent run over code.Bruce Momjian
1999-05-25*** empty log message ***Michael Meskes
1999-05-25Bugfix - Range table entries that are unused after rewriting shouldJan Wieck
not be marked inFromCl any longer. Otherwise the planner gets confused and joins over them where in fact it does not have to. Adjust hasSubLinks now with a recursive lookup - could be wrong in multi action rules because parse state isn't reset correctly and all actions in the rule are marked hasSubLinks if one of them has. Jan