summaryrefslogtreecommitdiff
path: root/src/backend/tcop
Commit message (Collapse)AuthorAgeFilesLines
* Hello.Bruce Momjian1999-10-261-10/+5
| | | | | | | | | | | | | | | | | | | 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-251-8/+8
| | | | | | | 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.
* Look Ma, no MAX_PARSE_BUFFER! (At least not in the backend.Tom Lane1999-10-231-9/+3
| | | | pg_dump and interfaces/odbc still need some work.)
* This patch implements ORACLE's COMMENT SQL command.Bruce Momjian1999-10-151-1/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | >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)
* Update display of debug levels.Bruce Momjian1999-10-081-3/+3
|
* clean up debug flags.Bruce Momjian1999-10-081-11/+3
|
* Cleanup -is flag to -l for SSL. Another PERL variable name fix. CleanBruce Momjian1999-10-081-10/+10
| | | | | up debugging options for postmaster and postgres programs. postmaster -d is no longer optional. Documentation updates.
* XLOG (also known as WAL -:)) Bootstrap/Startup/Shutdown.Vadim B. Mikheev1999-10-061-100/+126
| | | | | First step in cleaning up backend initialization code. Fix for FATAL: now FATAL is ERROR + exit.
* Hmm, guess I forgot to commit this file the other day ...Tom Lane1999-09-301-24/+19
| | | | just some cosmetic changes now, Vadim already fixed the heap_xxx calls.
* This is part #1 for of the DEFERRED CONSTRAINT TRIGGER support.Jan Wieck1999-09-292-3/+24
| | | | | | | | | | | | Implements the CREATE CONSTRAINT TRIGGER and SET CONSTRAINTS commands. TODO: Generic builtin trigger procedures Automatic execution of appropriate CREATE CONSTRAINT... at CREATE TABLE Support of new trigger type in pg_dump Swapping of huge # of events to disk Jan
* Transaction log manager core code.Vadim B. Mikheev1999-09-271-3/+3
| | | | It doesn't work currently but also don't break anything -:)
* Several changes here, not very related but touching some of the same files.Tom Lane1999-09-242-9/+20
| | | | | | | | | | | | | | | | | | | | | * Buffer refcount cleanup (per my "progress report" to pghackers, 9/22). * Add links to backend PROC structs to sinval's array of per-backend info, and use these links for routines that need to check the state of all backends (rather than the slow, complicated search of the ShmemIndex hashtable that was used before). Add databaseOID to PROC structs. * Use this to implement an interlock that prevents DESTROY DATABASE of a database containing running backends. (It's a little tricky to prevent a concurrently-starting backend from getting in there, since the new backend is not able to lock anything at the time it tries to look up its database in pg_database. My solution is to recheck that the DB is OK at the end of InitPostgres. It may not be a 100% solution, but it's a lot better than no interlock at all...) * In ALTER TABLE RENAME, flush buffers for the relation before doing the rename of the physical files, to ensure we don't get failures later from mdblindwrt(). * Update TRUNCATE patch so that it actually compiles against current sources :-(. You should do "make clean all" after pulling these changes.
* Add TRUNCATE command, with psql help and sgml additions.Bruce Momjian1999-09-231-1/+33
|
* Mega-commit to make heap_open/heap_openr/heap_close take anTom Lane1999-09-181-16/+17
| | | | | | | | | | | | | | | | | additional argument specifying the kind of lock to acquire/release (or 'NoLock' to do no lock processing). Ensure that all relations are locked with some appropriate lock level before being examined --- this ensures that relevant shared-inval messages have been processed and should prevent problems caused by concurrent VACUUM. Fix several bugs having to do with mismatched increment/decrement of relation ref count and mismatched heap_open/close (which amounts to the same thing). A bogus ref count on a relation doesn't matter much *unless* a SI Inval message happens to arrive at the wrong time, which is probably why we got away with this sloppiness for so long. Repair missing grab of AccessExclusiveLock in DROP TABLE, ALTER/RENAME TABLE, etc, as noted by Hiroshi. Recommend 'make clean all' after pulling this update; I modified the Relation struct layout slightly. Will post further discussion to pghackers list shortly.
* Commit the bulk of Mike Ansley's long-query changes in theTom Lane1999-08-311-65/+40
| | | | backend. Still much left to do.
* Plug several holes in backend's ability to cope withTom Lane1999-07-222-36/+56
| | | | unexpected loss of connection to frontend.
* Re-add getopt.h check, remove NT-specific tests for it.Bruce Momjian1999-07-191-3/+3
|
* Move some system includes into c.h, and remove duplicates.Bruce Momjian1999-07-174-11/+5
|
* Final cleanupBruce Momjian1999-07-161-3/+5
|
* Final cleanup.Bruce Momjian1999-07-165-51/+31
|
* Update #include cleanupsBruce Momjian1999-07-163-11/+11
|
* Remove unused #includes in *.c files.Bruce Momjian1999-07-155-52/+6
|
* Clean up #include in /include directory. Add scripts for checking includes.Bruce Momjian1999-07-155-17/+6
|
* Fix for removal of temp tables if last transaction was aborted.Bruce Momjian1999-07-021-13/+2
|
* 1. Run all pg_dump queries in single serializable transaction.Vadim B. Mikheev1999-05-291-2/+11
| | | | | | 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.
* Make functions static or NOT_USED as appropriate.Bruce Momjian1999-05-261-3/+4
|
* Another pgindent run. Sorry folks.Bruce Momjian1999-05-251-4/+4
|
* pgindent run over code.Bruce Momjian1999-05-254-65/+90
|
* Improve error message from failed LOAD command (includeTom Lane1999-05-221-13/+3
| | | | kernel's error description when file is not accessible).
* Modify backend switch parsing to prevent 'insecure' switchesTom Lane1999-05-221-106/+122
| | | | | from being accepted when they are passed from client connection request. Get rid of a couple that no longer do anything (like -P).
* Make postgres prompt backend>, and remove PARSEDEBUG.Bruce Momjian1999-05-221-3/+3
|
* Rip out QueryTreeList structure, root and branch. QuerytreeTom Lane1999-05-131-114/+55
| | | | | | | | | | lists are now plain old garden-variety Lists, allocated with palloc, rather than specialized expansible-array data allocated with malloc. This substantially simplifies their handling and eliminates several sources of memory leakage. Several basic types of erroneous queries (syntax error, attempt to insert a duplicate key into a unique index) now demonstrably leak zero bytes per query.
* Changed debug options:Jan Wieck1999-05-111-19/+53
| | | | | | | | | -d4 now prints compressed trees from nodeToString() -d5 prints pretty trees via nodeDisplay() new pg_options: pretty_plan, pretty_parse, pretty_rewritten Jan
* Change error messages to oids come out as %u and not %d. Change has noBruce Momjian1999-05-101-4/+4
| | | | real affect now.
* Rearrange top-level rewrite operations so that EXPLAIN worksTom Lane1999-05-091-86/+57
| | | | on queries involving UNION, EXCEPT, INTERSECT.
* here are some patches for 6.5.0 which I already submitted but have neverBruce Momjian1999-05-031-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | been applied. The patches are in the .tar.gz attachment at the end: varchar-array.patch this patch adds support for arrays of bpchar() and varchar(), which where always missing from postgres. These datatypes can be used to replace the _char4, _char8, etc., which were dropped some time ago. block-size.patch this patch fixes many errors in the parser and other program which happen with very large query statements (> 8K) when using a page size larger than 8192. This patch is needed if you want to submit queries larger than 8K. Postgres supports tuples up to 32K but you can't insert them because you can't submit queries larger than 8K. My patch fixes this problem. The patch also replaces all the occurrences of `8192' and `1<<13' in the sources with the proper constants defined in include files. You should now never find 8192 hardwired in C code, just to make code clearer. -- Massimo Dal Zotto
* -T was omitted from getopt() call.Tom Lane1999-05-011-19/+24
|
* Fix stupid typo that broke empty-query response... odd thatTom Lane1999-04-281-2/+2
| | | | this is not revealed by any of our regression tests...
* Still had a few MULTIBYTE problems when client encoding wasTom Lane1999-04-251-3/+3
| | | | different from database's ...
* My first cut at libpq revision didn't handle MULTIBYTE correctly,Tom Lane1999-04-251-3/+2
| | | | but I think it's OK now...
* Revise backend libpq interfaces so that messages to the frontendTom Lane1999-04-253-44/+63
| | | | | | can be generated in a buffer and then sent to the frontend in a single libpq call. This solves problems with NOTICE and ERROR messages generated in the middle of a data message or COPY OUT operation.
* Change elog(ERROR) to get back to main loop via a plain sigsetjmp,Tom Lane1999-04-201-15/+13
| | | | | | instead of doing a kill(self, SIGQUIT) and expecting the signal handler to do it. Also, clean up inconsistent definitions of the sigjmp buffer in the several files that already referenced it.
* cleanupsBruce Momjian1999-03-231-3/+2
|
* Hi,Bruce Momjian1999-03-221-3/+3
| | | | | | | | | | I have solved some problems with dynamic loading on NT. It is possible to run succesfully both trigger and plpgsql regression tests. The patch is in the included file "diff". Dan
* Add new postgres -O option to allow system table structure changes.Bruce Momjian1999-03-172-8/+17
|
* Here is a patch.Bruce Momjian1999-03-161-9/+9
| | | | | | | | I have changed to call pg_exec_query_dest() instead of pg_exec_query(). Thanks. Hiroshi Inoue
* Remove reference to recipe.h.Bruce Momjian1999-02-251-2/+1
|
* Fix problem with selectivity error in added columns with ALTER TABLE.Bruce Momjian1999-02-241-1/+3
| | | | Move files to deadcode.
* From: Tatsuo Ishii <t-ishii@sra.co.jp>Marc G. Fournier1999-02-211-7/+7
| | | | | | Ok. I made patches replacing all of "#if FALSE" or "#if 0" to "#ifdef NOT_USED" for current. I have tested these patches in that the postgres binaries are identical.
* Enable bushy and right-hand queries by default.Bruce Momjian1999-02-181-4/+4
|
View Lorry Controller Status