summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Hello.Bruce Momjian1999-10-2615-238/+1039
| | | | | | | | | | | | | | | | | | | 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-2522-193/+183
| | | | | | | 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-253-5/+5
| | | | | 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-252-3/+5
|
* Add a notion of a 'catalog version number' that can indicateTom Lane1999-10-243-11/+90
| | | | | | | | | 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-241-1/+8
| | | | might think ... in fact doesn't do much of anything at the moment ...
* Remove gratuitous redefinitions of BLCKSZ.Tom Lane1999-10-232-2/+1
|
* Look Ma, no MAX_PARSE_BUFFER! (At least not in the backend.Tom Lane1999-10-2322-182/+127
| | | | pg_dump and interfaces/odbc still need some work.)
* Backup psql banner change.Bruce Momjian1999-10-231-3/+4
|
* Remove fixed-size literal buffer from ecpg's lexer (sameTom Lane1999-10-222-84/+107
| | | | | | | | 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-221-1/+0
|
* This *should* fix the large binary object problem in libpq++ from theBruce Momjian1999-10-222-6/+4
| | | | | | TODO list. Vince
* I have a patch for postgresql-snapshot(1999-10-22).Bruce Momjian1999-10-221-5/+11
| | | | | | | | | | | | 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
* Update TODO list.Bruce Momjian1999-10-221-2/+2
|
* Another day, another MAX_QUERY_SIZE dependency zapped.Tom Lane1999-10-221-15/+22
|
* Update TODO list.Bruce Momjian1999-10-211-1/+2
|
* Bugfix for CREATE RULE invoked via SPI --- from Hiroshi,Tom Lane1999-10-211-2/+3
| | | | 23 Jul 99. Not sure why this didn't get applied before...
* Remove fixed-size buffers in rule storage routine.Tom Lane1999-10-211-35/+40
|
* change issue to information in bannerBruce Momjian1999-10-211-2/+2
|
* Make psql startup banner cleaner.Bruce Momjian1999-10-211-4/+3
|
* BufFileSeek's behavior at segment boundaries wasn't whatTom Lane1999-10-191-13/+26
| | | | logfile.c wanted ... seems easier to fix BufFileSeek.
* Update \dT again.Bruce Momjian1999-10-181-3/+3
|
* More \dT cleanupBruce Momjian1999-10-181-6/+6
|
* Clean up \dT display.Bruce Momjian1999-10-181-21/+21
|
* Make bpchar == char() clearer in \dT display.Bruce Momjian1999-10-181-3/+3
|
* Drive a stake through the heart of the last use of MAX_PARSE_BUFFERTom Lane1999-10-181-21/+25
| | | | | in the backend. Still a few stragglers, but we're getting closer to being rid of query length limits...
* Remove fixed-size literal buffer from scan.l, and repairTom Lane1999-10-182-62/+73
| | | | | | | | boundary-condition bug in myinput() which caused flex scanner to fail on tokens larger than a bufferload. Turns out flex doesn't want null- terminated input ... and if it gives you a 1-character buffer, you'd better supply a character, not a null, lest you be thought to be reporting end of input.
* Update TODO list.Bruce Momjian1999-10-183-3/+12533
|
* Except_Intersect_Rewrite() forgot to move LIMIT info to newTom Lane1999-10-171-1/+8
| | | | topmost SELECT node after rearranging query tree.
* Change fd.c so that temp files are closed and deleted atTom Lane1999-10-171-5/+9
| | | | | | | proc_exit time. I discovered that if the frontend closes the connection when you're inside a transaction block, there is nothing ensuring that temp files go away ... I wonder whether proc_exit ought to try to do an explicit transaction abort?
* Remove now-dead sort modules.Tom Lane1999-10-175-1479/+0
|
* Final stage of psort reconstruction work: replace psort.c withTom Lane1999-10-1710-1018/+1747
| | | | | | | a generalized module 'tuplesort.c' that can sort either HeapTuples or IndexTuples, and is not tied to execution of a Sort node. Clean up memory leakages in sorting, and replace nbtsort.c's private implementation of mergesorting with calls to tuplesort.c.
* Actually, nodeMergejoin shouldn't include psort.h at all...Tom Lane1999-10-171-2/+1
|
* nodeMergejoin was depending on an inclusion from psort.h...Tom Lane1999-10-161-1/+2
|
* Second phase of psort reconstruction project: add bookkeeping logic toTom Lane1999-10-167-452/+1293
| | | | | | recycle storage within sort temp file on a block-by-block basis. This reduces peak disk usage to essentially just the volume of data being sorted, whereas it had been about 4x the data volume before.
* Check RELSEG_SIZE when postmaster starting up.Tatsuo Ishii1999-10-161-0/+10
| | | | | this is neccesary to make sure that the backend and the database uses same RELSEG_SIZE.
* *** empty log message ***Michael Meskes1999-10-156-55/+99
|
* Fix typo in descriptions.Bruce Momjian1999-10-151-2/+2
|
* Clean up type descriptions.Bruce Momjian1999-10-152-4/+5
|
* This patch implements ORACLE's COMMENT SQL command.Bruce Momjian1999-10-1512-21/+287
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | >From the ORACLE 7 SQL Language Reference Manual: ----------------------------------------------------- COMMENT Purpose: To add a comment about a table, view, snapshot, or column into the data dictionary. Prerequisites: The table, view, or snapshot must be in your own schema or you must have COMMENT ANY TABLE system privilege. Syntax: COMMENT ON [ TABLE table ] | [ COLUMN table.column] IS 'text' You can effectively drop a comment from the database by setting it to the empty string ''. ----------------------------------------------------- Example: COMMENT ON TABLE workorders IS 'Maintains base records for workorder information'; COMMENT ON COLUMN workorders.hours IS 'Number of hours the engineer worked on the task'; to drop a comment: COMMENT ON COLUMN workorders.hours IS ''; The current patch will simply perform the insert into pg_description, as per the TODO. And, of course, when the table is dropped, any comments relating to it or any of its attributes are also dropped. I haven't looked at the ODBC source yet, but I do know from an ODBC client standpoint that the standard does support the notion of table and column comments. Hopefully the ODBC driver is already fetching these values from pg_description, but if not, it should be trivial. Hope this makes the grade, Mike Mascari (mascarim@yahoo.com)
* Add S-tree doc for possible future use.Bruce Momjian1999-10-151-0/+0
|
* Update psql \? for \w.Bruce Momjian1999-10-142-4/+4
|
* Correctly return -1 on error to CmdTuples()Bruce Momjian1999-10-131-2/+2
| | | | Vince.
* Split 'BufFile' routines out of fd.c into a new module, buffile.c. ExtendTom Lane1999-10-1312-318/+707
| | | | | | | | BufFile so that it handles multi-segment temporary files transparently. This allows sorts and hashes to work with data exceeding 2Gig (or whatever the local limit on file size is). Change psort.c to use relative seeks instead of absolute seeks for backwards scanning, so that it won't fail when the data volume exceeds 2Gig.
* Hi,Bruce Momjian1999-10-135-14/+8
| | | | | | | | | | | | I have changed a bit the makefiles for the win32 port - the *.def files (created when building shared libraries) are now clean from Makefile.shlib. I have also removed "-g" from CFLAGS in the "cygwin32" template - it can be enabled when running configure. Dan
* Update jdbc for release version #>Bruce Momjian1999-10-131-0/+2
|
* Update for NUMERIC/DECIMAL data type.Bruce Momjian1999-10-131-10/+22
|
* BLOBs containing NUL characters (ASCII 0) can be written to theBruce Momjian1999-10-131-3/+3
| | | | | | | | | | | | | | | | | | | | | database, but they get truncated at the first NUL by lo_read when they are read back. The reason for this is that lo_read in Pg.xs is using the default: OUTPUT: RETVAL buf which uses C's strlen() to work out the length of the scalar. The code ought to read something more like: OUTPUT: RETVAL buf sv_setpvn((SV*)ST(2), buf, RETVAL); I am not sure if this needs to be done on both lo_read methods in this file, but I changed both and have not since had any problems with truncated BLOBs. Douglas Thomson <dougt@mugc.cc.monash.edu.au>
* Update new HISTORY file.Bruce Momjian1999-10-121-1934/+1912
|
* Update sgml.Bruce Momjian1999-10-121-8/+2
|
View Lorry Controller Status