summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* cleanup of pgeasy.Bruce Momjian1999-10-111-35/+1
|
* Update again.Bruce Momjian1999-10-111-2/+2
|
* pgeasy update.Bruce Momjian1999-10-1111-3/+3
|
* Update pgeasy.Bruce Momjian1999-10-111-2/+2
|
* autoconfBruce Momjian1999-10-111-0/+2
|
* Add pginterface into main tree, called pgeasy.Bruce Momjian1999-10-1115-5/+888
|
* The 1st step to implement new type of scan,TidScan.Hiroshi Inoue1999-10-116-10/+238
| | | | | Now WHERE restriction on ctid is allowed though it is sequentially scanned.
* Improve pg_dump template1 error reports.Bruce Momjian1999-10-101-4/+9
|
* Re-add mention of FAQ's for shared memory/ipc errors.Bruce Momjian1999-10-101-6/+9
|
* Improve pg_dump template1 error message.Bruce Momjian1999-10-101-4/+6
|
* Allow \r as whitespace.Bruce Momjian1999-10-091-2/+2
|
* Move __alpha to port/alpha.h.Bruce Momjian1999-10-092-5/+6
|
* Define __alpha__ for __alpha.Bruce Momjian1999-10-082-2/+8
|
* First real FOREIGN KEY constraint trigger functionality.Jan Wieck1999-10-081-12/+942
| | | | | | | | | Implemented now: FOREIGN KEY ... REFERENCES ... MATCH FULL FOREIGN KEY ... MATCH FULL ... ON DELETE CASCADE Jan
* *** empty log message ***Michael Meskes1999-10-089-441/+293
|
* Update display of debug levels.Bruce Momjian1999-10-082-5/+5
|
* clean up debug flags.Bruce Momjian1999-10-081-11/+3
|
* Comment cleanup.Bruce Momjian1999-10-081-3/+3
|
* Fix for "--" comment and no trailing newline, as seen in Perl.Bruce Momjian1999-10-082-4/+4
|
* Cleanup -is flag to -l for SSL. Another PERL variable name fix. CleanBruce Momjian1999-10-085-35/+31
| | | | | up debugging options for postmaster and postgres programs. postmaster -d is no longer optional. Documentation updates.
* Remove a no-longer-needed kluge for degenerate aggregate cases,Tom Lane1999-10-082-23/+12
| | | | and update some comments.
* More startup/shutdown log messages.Vadim B. Mikheev1999-10-081-10/+43
|
* Use $(PERL) variable for perl compile. Now in Makefile.global.Bruce Momjian1999-10-081-2/+2
|
* Somehow missed this call to addRangeTableEntry() ...Tom Lane1999-10-071-2/+2
|
* Fix planner and rewriter to follow SQL semantics for tables that areTom Lane1999-10-0721-380/+398
| | | | | | | | | | | mentioned in FROM but not elsewhere in the query: such tables should be joined over anyway. Aside from being more standards-compliant, this allows removal of some very ugly hacks for COUNT(*) processing. Also, allow HAVING clause without aggregate functions, since SQL does. Clean up CREATE RULE statement-list syntax the same way Bruce just fixed the main stmtmulti production. CAUTION: addition of a field to RangeTblEntry nodes breaks stored rules; you will have to initdb if you have any rules.
* Small cleanup.Vadim B. Mikheev1999-10-061-2/+6
|
* XLOG (also known as WAL -:)) Bootstrap/Startup/Shutdown.Vadim B. Mikheev1999-10-0620-979/+1122
| | | | | First step in cleaning up backend initialization code. Fix for FATAL: now FATAL is ERROR + exit.
* More more liszt language code, so remove it from pg_language.Bruce Momjian1999-10-061-3/+1
|
* Improve the treatment of partial(incomplete) blocks of relation files.Hiroshi Inoue1999-10-061-5/+22
| | | | | This may solve a TODO item * Recover or force failure when disk space is exhausted
* Don't set BootstrapProcessingMode in AddNewRelationTuple() beforeVadim B. Mikheev1999-10-061-18/+4
| | | | | heap_insert() any more. No reasons to do it, and old comments said about this.
* CmdTuples() returns an int showing the number of affected tuples after anBruce Momjian1999-10-063-4/+11
| | | | | | | | insert, update or delete. It will return -1 on error, although I've yet to an error situation to prove that out! Vince
* Allow comment-only lines, and ;;; lines too.Bruce Momjian1999-10-051-8/+19
|
* As we now use lipq++.H which wasn't around when I first posted theBruce Momjian1999-10-041-1/+3
| | | | | | 2 line GetIsNull diffs, we now need this too: Patrick Welche
* Less noisy rule display...Tom Lane1999-10-041-51/+51
|
* Make the rule deparser a little less quote-happy, so thatTom Lane1999-10-041-63/+147
| | | | display of default expressions isn't quite so ugly.
* Oops, DEFAULT processing wasn't doing type compatibility checkingTom Lane1999-10-041-17/+41
| | | | | | quite the same way that transformInsertStatement does, so that an expression could be accepted by CREATE TABLE and then fail when used. Also, put back check that CONSTRAINT expressions must yield boolean...
* Reimplement parsing and storage of default expressions and constraintTom Lane1999-10-0318-886/+923
| | | | | | | | | | | | | | | expressions in CREATE TABLE. There is no longer an emasculated expression syntax for these things; it's full a_expr for constraints, and b_expr for defaults (unfortunately the fact that NOT NULL is a part of the column constraint syntax causes a shift/reduce conflict if you try a_expr. Oh well --- at least parenthesized boolean expressions work now). Also, stored expression for a column default is not pre-coerced to the column type; we rely on transformInsertStatement to do that when the default is actually used. This means "f1 datetime default 'now'" behaves the way people usually expect it to. BTW, all the support code is now there to implement ALTER TABLE ADD CONSTRAINT and ALTER TABLE ADD COLUMN with a default value. I didn't actually teach ALTER TABLE to call it, but it wouldn't be much work.
* autoconfBruce Momjian1999-10-031-403/+428
|
* I hope this is what you had in mind:Bruce Momjian1999-10-031-0/+21
| | | | | | | | | | | | | | --enable-debug adds -g (unconditionally) --disable-debug removes -g (if it was already in there somehow) (giving neither does nothing) Since none of the templates default CFLAGS with a -g you're not likely to end up with two -g flags. Not that they'd hurt though. It doesn't do anything about C++. Peter Eisentraut
* Teach parse_coerce about non-cachable functions (actually,Tom Lane1999-10-022-33/+18
| | | | make it call eval_const_expressions() so that it doesn't have to know).
* Allow CREATE FUNCTION's WITH clause to be used for all language types,Tom Lane1999-10-027-137/+117
| | | | | | | not just C, so that ISCACHABLE attribute can be specified for user-defined functions. Get rid of ParamString node type, which wasn't actually being generated by gram.y anymore, even though define.c thought that was what it was getting. Clean up minor bug in dfmgr.c (premature heap_close).
* Replace float.c's #ifdef finite check with a proper autoconf check, so itTom Lane1999-10-024-88/+121
| | | | works if finite() is a function. Patch from Christof Petig.
* Stick finger into a couple more holes in the leaky dike ofTom Lane1999-10-021-1/+16
| | | | | | | modifyAggrefQual. This routine really, really needs to be retired, but until we have subselects in FROM there's no chance of doing the job right. In the meantime try to respond to unhandlable cases with elog rather than coredump.
* Fix make_clause and make_opclause to record valid type infoTom Lane1999-10-021-20/+22
| | | | | | | in the Expr nodes they produce. This fixes a few cases of errors like 'typeidTypeRelid: Invalid type - oid = 0' caused by calling parser-related routines on expression trees that have already been processed by planner- related routines.
* Revise rule-printing routines to use expandable StringInfo buffers, so thatTom Lane1999-10-022-431/+369
| | | | | | | they have no hardwired limit on the length of a rule's text. Fix a couple of minor bugs in passing --- deparsed UPDATE queries didn't have quotes around relation name, and quotes and backslashes in constant values weren't backslash-quoted.
* Clean up rewriter routines to use expression_tree_walker andTom Lane1999-10-014-2443/+965
| | | | | | | | | | | | expression_tree_mutator rather than ad-hoc tree walking code. This shortens the code materially and fixes a fair number of sins of omission. Also, change modifyAggrefQual to *not* recurse into subselects, since its mission is satisfied if it removes aggregate functions from the top level of a WHERE clause. This cures problems with queries of the form SELECT ... WHERE x IN (SELECT ... HAVING something-using-an-aggregate), which would formerly get mucked up by modifyAggrefQual. The routine is still fundamentally broken, of course, but I don't think there's any way to get rid of it before we implement subselects in FROM ...
* Fixed opr_sanity regression test to ignore the newJan Wieck1999-09-302-2/+4
| | | | | | | RI_FKey_... constrint triggers when looking for illegal pg_proc entries. Jan
* Added utils/adt/ri_triggers with empty shells for theJan Wieck1999-09-305-6/+226
| | | | | | | | FOREIGN KEY triggers. Added pg_proc entries for all the new functions. Jan
* Removed (useless) pg_proc_prosrc_indexJan Wieck1999-09-305-48/+26
| | | | Jan
* Reverse out getopt patch --- turns out it doesn't help on myTom Lane1999-09-301-2/+2
| | | | | platform, and there are at least some people it's not broken for. So undo change until we can discuss a more portable solution.
View Lorry Controller Status