aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Allow indexes on system catalogs for use in cache code.Bruce Momjian1999-11-01
| | | | Thanks to Hiroshi
* autoconfBruce Momjian1999-10-31
|
* Update to pgaccess 0.98.Bruce Momjian1999-10-31
|
* Rule dumper failed to affix '*' to inheritable RTEs.Tom Lane1999-10-31
|
* Update for 0.98 pgaccessBruce Momjian1999-10-31
|
* Update for 0.98.Bruce Momjian1999-10-31
|
* autoconfBruce Momjian1999-10-31
|
* Update pgaccess makefile for 0.98Bruce Momjian1999-10-31
|
* Avoid duplicate ExecTypeFromTL() call in ExecInitJunkFilter() by passingTom Lane1999-10-30
| | | | | | | in the TupleDesc that the caller already has (for call from ExecMain) or can make just as easily as ExecInitJunkFilter() can (for call from ExecAppend). Also, don't bother to build a junk filter for an INSERT operation that doesn't actually need one, which is the normal case.
* Rearrange heap_beginscan to eliminate extra call onTom Lane1999-10-30
| | | | | mdnblocks. Bad enough it does an lseek, but to do it twice for no reason...
* Skip invoking set_uppernode_references() for a RESULT nodeTom Lane1999-10-30
| | | | | that has no subplan --- saves a material amount of time for a simple INSERT ... VALUES query.
* Rewrite preprocess_targetlist() to reduce overhead for simple INSERTs.Tom Lane1999-10-30
| | | | | | In particular, don't bother to look up type information for attributes where we're not actually going to use it, and avoid copying entire tlist structure when it's not necessary.
* Update pgaccess for 0.98.Bruce Momjian1999-10-30
|
* Further performance improvements in sorting: reduce number of comparisonsTom Lane1999-10-30
| | | | | | | | during initial run formation by keeping both current run and next-run tuples in the same heap (yup, Knuth is smarter than I am). And, during merge passes, make use of available sort memory to load multiple tuples from any one input 'tape' at a time, thereby improving locality of access to the temp file.
* Add pgaccess Makefile.Bruce Momjian1999-10-30
|
* Add 0.98.Bruce Momjian1999-10-30
|
* Remove 0.96 for update to 0.98Bruce Momjian1999-10-30
|
* Ooops ... 6.5 coding wasn't quite right anymore. Should learnTom Lane1999-10-30
| | | | never to commit without running regress tests...
* Put back code in nodeAgg to generate a dummy all-nulls input tupleTom Lane1999-10-30
| | | | | | | before calling execProject, when the outerPlan has returned zero tuples. I took this out under the mistaken impression that the input tuple couldn't be referenced by execProject if we weren't in GROUP BY mode. But it can, if we're in an UPDATE or DELETE...
* Make USING in COPY optional.Bruce Momjian1999-10-29
|
* Fix wording.Bruce Momjian1999-10-29
|
* *** empty log message ***Michael Meskes1999-10-29
|
* Fix psql quote missing.Bruce Momjian1999-10-27
|
* *** empty log message ***Michael Meskes1999-10-27
|
* Fix compile after COMMENT problem.Bruce Momjian1999-10-26
|
* These are two minor corrections to libpq's PQsetNoticeProcessor function.Bruce Momjian1999-10-26
| | | | | | | | | | | | One, it now returns the previous hook. That way people don't have to dig around in libpq-int.h for that information anymore. It previously returned void, so there should be no incompatibilities. Second, you cannot set the callback to NULL anymore. (Of course you can still call it with NULL just to get the current hook.) The way libpq uses the callback pointer, having a NULL there wasn't very healthy. Peter Eisentraut
* improve manual pageBruce Momjian1999-10-26
|
* Add documentation for comment.Bruce Momjian1999-10-26
|
* Hello.Bruce Momjian1999-10-26
| | | | | | | | | | | | | | | | | | | The following patch extends the COMMENT ON functionality to the rest of the database objects beyond just tables, columns, and views. The grammer of the COMMENT ON statement now looks like: COMMENT ON [ [ DATABASE | INDEX | RULE | SEQUENCE | TABLE | TYPE | VIEW ] <objname> | COLUMN <relation>.<attribute> | AGGREGATE <aggname> <aggtype> | FUNCTION <funcname> (arg1, arg2, ...) | OPERATOR <op> (leftoperand_typ rightoperand_typ) | TRIGGER <triggername> ON relname> Mike Mascari (mascarim@yahoo.com)
* Standardize on MAXPGPATH as the size of a file pathname buffer,Tom Lane1999-10-25
| | | | | | | eliminating some wildly inconsistent coding in various parts of the system. I set MAXPGPATH = 1024 in config.h.in. If anyone is really convinced that there ought to be a configure-time test to set the value, go right ahead ... but I think it's a waste of time.
* 'extern char *pg_pathname' in these files fails to agree withTom Lane1999-10-25
| | | | | postgres.c's declaration of 'char pg_pathname[...]'. I dunno when these ports were last used, but they are sure broken now...
* bug fix for large objects (free)Byron Nikolaidis1999-10-25
|
* Add a notion of a 'catalog version number' that can indicateTom Lane1999-10-24
| | | | | | | | | when an initdb-forcing change has been applied within a development cycle. PG_VERSION serves this purpose for official releases, but we can't bump the PG_VERSION number every time we make a change to the catalogs during development. Instead, increase the catalog version number to warn other developers that you've made an incompatible change. See my mail to pghackers for more info.
* Add comment explaining that this table doesn't do what youTom Lane1999-10-24
| | | | might think ... in fact doesn't do much of anything at the moment ...
* Remove gratuitous redefinitions of BLCKSZ.Tom Lane1999-10-23
|
* Look Ma, no MAX_PARSE_BUFFER! (At least not in the backend.Tom Lane1999-10-23
| | | | pg_dump and interfaces/odbc still need some work.)
* Backup psql banner change.Bruce Momjian1999-10-23
|
* Remove fixed-size literal buffer from ecpg's lexer (sameTom Lane1999-10-22
| | | | | | | | fix recently applied to backend's lexer). I see that YY_USES_REJECT still gets defined for this lexer, which means it's going to have trouble parsing really long tokens. Not sure if it's worth doing anything about that or not; I don't have the interest right now to understand why ecpg's additions to the syntax cause this problem...
* Remove libpq++ todo item.Bruce Momjian1999-10-22
|
* This *should* fix the large binary object problem in libpq++ from theBruce Momjian1999-10-22
| | | | | | TODO list. Vince
* I have a patch for postgresql-snapshot(1999-10-22).Bruce Momjian1999-10-22
| | | | | | | | | | | | This patch fix a TODO list item. * require SELECT DISTINCT target list to have all ORDER BY columns example ogawa=> select distinct x from t1 order by y; ERROR: ORDER BY columns must appear in SELECT DISTINCT target list --- Atsushi Ogawa
* Another day, another MAX_QUERY_SIZE dependency zapped.Tom Lane1999-10-22
|
* Bugfix for CREATE RULE invoked via SPI --- from Hiroshi,Tom Lane1999-10-21
| | | | 23 Jul 99. Not sure why this didn't get applied before...
* Remove fixed-size buffers in rule storage routine.Tom Lane1999-10-21
|
* change issue to information in bannerBruce Momjian1999-10-21
|
* Make psql startup banner cleaner.Bruce Momjian1999-10-21
|
* BufFileSeek's behavior at segment boundaries wasn't whatTom Lane1999-10-19
| | | | logfile.c wanted ... seems easier to fix BufFileSeek.
* Update \dT again.Bruce Momjian1999-10-18
|
* More \dT cleanupBruce Momjian1999-10-18
|
* Clean up \dT display.Bruce Momjian1999-10-18
|