| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Vince.
|
|
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.
|
|
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
|
|
|
|
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>
|
|
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
|
|
|
|
|
|
|
|
|
|
as BLCKSZ which the backend was compiled in.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now WHERE restriction on ctid is allowed though it is
sequentially scanned.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Implemented now:
FOREIGN KEY ... REFERENCES ... MATCH FULL
FOREIGN KEY ... MATCH FULL ... ON DELETE CASCADE
Jan
|
|
|
|
|
|
|
|
|
|
|
|
up debugging options for postmaster and postgres programs. postmaster
-d is no longer optional. Documentation updates.
|
|
and update some comments.
|
|
|
|
|
|
|
|
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.
|
|
|
|
First step in cleaning up backend initialization code.
Fix for FATAL: now FATAL is ERROR + exit.
|
|
|
|
This may solve a TODO item
* Recover or force failure when disk space is exhausted
|
|
heap_insert() any more. No reasons to do it, and old comments
said about this.
|
|
insert, update or delete. It will return -1 on error, although I've yet
to an error situation to prove that out!
Vince
|
|
|
|
2 line GetIsNull diffs, we now need this too:
Patrick Welche
|
|
|
|
display of default expressions isn't quite so ugly.
|
|
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...
|
|
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.
|
