aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Update psql \? for \w.Bruce Momjian1999-10-14
|
* Correctly return -1 on error to CmdTuples()Bruce Momjian1999-10-13
| | | | Vince.
* Split 'BufFile' routines out of fd.c into a new module, buffile.c. ExtendTom Lane1999-10-13
| | | | | | | | 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-13
| | | | | | | | | | | | 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-13
|
* BLOBs containing NUL characters (ASCII 0) can be written to theBruce Momjian1999-10-13
| | | | | | | | | | | | | | | | | | | | | 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>
* I have created a small patch that makes possible to compile pgsql on newerBruce Momjian1999-10-12
| | | | | | | | | | | Cygwin snapshots (tested on 990115 which is recommended to use - it fixes some errors in B20.1) And I have another patch for including <sys/ipc.h> before <sys/sem.h> in backend/storage/lmgr/proc.c - it is required due the design of cygipc headers Dan
* Remove pgeasy Makefile on distclean.Bruce Momjian1999-10-12
|
* autoconfBruce Momjian1999-10-12
|
* autoconfBruce Momjian1999-10-12
|
* Update pgeasy for missing files.Bruce Momjian1999-10-12
|
* Add blcksz to struct ControlFileData to check BLCKSZ is sameTatsuo Ishii1999-10-12
| | | | as BLCKSZ which the backend was compiled in.
* Update pgeasy.Bruce Momjian1999-10-11
|
* cleanup of pgeasy.Bruce Momjian1999-10-11
|
* Update again.Bruce Momjian1999-10-11
|
* pgeasy update.Bruce Momjian1999-10-11
|
* Update pgeasy.Bruce Momjian1999-10-11
|
* autoconfBruce Momjian1999-10-11
|
* Add pginterface into main tree, called pgeasy.Bruce Momjian1999-10-11
|
* The 1st step to implement new type of scan,TidScan.Hiroshi Inoue1999-10-11
| | | | | Now WHERE restriction on ctid is allowed though it is sequentially scanned.
* Improve pg_dump template1 error reports.Bruce Momjian1999-10-10
|
* Re-add mention of FAQ's for shared memory/ipc errors.Bruce Momjian1999-10-10
|
* Improve pg_dump template1 error message.Bruce Momjian1999-10-10
|
* Allow \r as whitespace.Bruce Momjian1999-10-09
|
* Move __alpha to port/alpha.h.Bruce Momjian1999-10-09
|
* Define __alpha__ for __alpha.Bruce Momjian1999-10-08
|
* First real FOREIGN KEY constraint trigger functionality.Jan Wieck1999-10-08
| | | | | | | | | Implemented now: FOREIGN KEY ... REFERENCES ... MATCH FULL FOREIGN KEY ... MATCH FULL ... ON DELETE CASCADE Jan
* *** empty log message ***Michael Meskes1999-10-08
|
* Update display of debug levels.Bruce Momjian1999-10-08
|
* clean up debug flags.Bruce Momjian1999-10-08
|
* Comment cleanup.Bruce Momjian1999-10-08
|
* Fix for "--" comment and no trailing newline, as seen in Perl.Bruce Momjian1999-10-08
|
* Cleanup -is flag to -l for SSL. Another PERL variable name fix. CleanBruce Momjian1999-10-08
| | | | | 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-08
| | | | and update some comments.
* More startup/shutdown log messages.Vadim B. Mikheev1999-10-08
|
* Use $(PERL) variable for perl compile. Now in Makefile.global.Bruce Momjian1999-10-08
|
* Somehow missed this call to addRangeTableEntry() ...Tom Lane1999-10-07
|
* Fix planner and rewriter to follow SQL semantics for tables that areTom Lane1999-10-07
| | | | | | | | | | | 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-06
|
* XLOG (also known as WAL -:)) Bootstrap/Startup/Shutdown.Vadim B. Mikheev1999-10-06
| | | | | 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-06
|
* Improve the treatment of partial(incomplete) blocks of relation files.Hiroshi Inoue1999-10-06
| | | | | 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-06
| | | | | 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-06
| | | | | | | | 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-05
|
* As we now use lipq++.H which wasn't around when I first posted theBruce Momjian1999-10-04
| | | | | | 2 line GetIsNull diffs, we now need this too: Patrick Welche
* Less noisy rule display...Tom Lane1999-10-04
|
* Make the rule deparser a little less quote-happy, so thatTom Lane1999-10-04
| | | | display of default expressions isn't quite so ugly.
* Oops, DEFAULT processing wasn't doing type compatibility checkingTom Lane1999-10-04
| | | | | | 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-03
| | | | | | | | | | | | | | | 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.
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-26 06:20:36 +0000