| Age | Commit message (Collapse) | Author |
|---|
|
incarnations (I hope). When an acceptable flex version is not found, print
instructive error messages from both configure and the makefiles, so that
users can continue building anyway.
|
|
a reasonable error message (including the kernel errno message)
is reported on any file open failure.
|
|
virtual FDs, we just return the ENFILE/EMFILE error to the caller,
rather than immediate elog(). This allows more robust behavior in
the postmaster, which uses AllocateFile() but does not want elog().
|
|
the harm potential outweighs the possible benefits.
|
|
to int so that they return the number of whcars.
|
|
|
|
on some platforms.
|
|
recent change to geometry.sql.
|
|
packages can use to configure their build.
E.g.,
$ pg-config --libdir
/usr/local/pgsql/lib
`pg-config --configure' stores the configure command line.
|
|
equal keys. See discussion of today's date in pghackers list.
|
|
length is < TOAST_TUPLE_THRESHOLD, even with toastable column types
present. For example, CREATE TABLE foo (f1 int, f2 varchar(100))
does not require a toast table, even though varchar is a toastable
type.
|
|
pg_mb2wchar(const unsigned char *, pg_wchar *);
pg_mb2wchar_with_len(const unsigned char *, pg_wchar *, int);
from void to int. Now they return the number of
wide chars.
|
|
(rather than compile time). For libpq, even when Kerberos support is
compiled in, the default user name should still fall back to geteuid()
if it can't be determined via the Kerberos system.
A couple of fixes for string type configuration parameters, now that there
is one.
|
|
Datum, not char*, for portability's sake.
|
|
|
|
for example, an SQL function can be used in a functional index. (I make
no promises about speed, but it'll work ;-).) Clean up and simplify
handling of functions returning sets.
|
|
Remove hardcoded macaddr_manuf(), which had really old, obsolete info.
Replace this with some contrib/mac/ code to maniag OUI info from IEEE.
|
|
newlines.
|
|
multibyte sequence while truncating identifiers.
|
|
incorrect multibyte sequence while truncating too long names.
|
|
Eliminate up-to-4-times memory allocation problem
|
|
right circumstances a hash join executed as a DECLARE CURSOR/FETCH
query would crash the backend. Problem as seen in current sources was
that the hash tables were stored in a context that was a child of
TransactionCommandContext, which got zapped at completion of the FETCH
command --- but cursor cleanup executed at COMMIT expected the tables
to still be valid. I haven't chased down the details as seen in 7.0.*
but I'm sure it's the same general problem.
|
|
|
|
pg_proc.c (where it's actually used). Fix it to correctly handle tlists
that contain resjunk target items, and improve error messages. This
addresses bug reported by Krupnikov 6-July-00.
|
|
Also, make it depend on type OIDs rather than type names for more
consistency with rest of backend.
|
|
macros where appropriate (the code used to have several different ways
of doing that, including Int32, Int8, UInt8, ...). Remove last few
references to float32 and float64 typedefs --- it's all float4/float8
now. The typedefs themselves should probably stay in c.h for a release
or two, though, to avoid breaking user-written C functions.
|
|
Update functions to new-style fmgr, make BIT and VARBIT be binary-
equivalent, add entries to allow these types to be btree indexed,
correct a few bugs. BIT/VARBIT are now toastable, too.
NOTE: initdb forced due to catalog updates.
|
|
|
|
PGLIB or use any option anymore.
|
|
unsupported platforms.
|
|
CREATE INDEX fooi ON foo (lower(f1)) where f1 is varchar rather than text.
|
|
right thing with variable-free clauses that contain noncachable functions,
such as 'WHERE random() < 0.5' --- these are evaluated once per
potential output tuple. Expressions that contain only Params are
now candidates to be indexscan quals --- for example, 'var = ($1 + 1)'
can now be indexed. Cope with RelabelType nodes atop potential indexscan
variables --- this oversight prevents 7.0.* from recognizing some
potentially indexscanable situations.
|
|
take 'em out of pg_operator. Also remove from scan.l's set of legal
operator characters. Update documentation.
|
|
as UPDATE foo SET arr[3] = 42.
|
|
|
|
including utility statements. Still can't copy or compare executor
state, but at present that doesn't seem to be necessary. This makes
it possible to execute most (all?) utility statements in plpgsql.
Had to change parsetree representation of CreateTrigStmt so that it
contained only legal Nodes, and not bare string constants.
|
|
first place :-(
|
|
backwards compatibility with old behavior.
|
|
are running.
|
|
|
|
from Param nodes, per discussion a few days ago on pghackers. Add new
expression node type FieldSelect that implements the functionality where
it's actually needed. Clean up some other unused fields in Func nodes
as well.
NOTE: initdb forced due to change in stored expression trees for rules.
|
|
|
|
as MaxHeapAttributeNumber. Increase MaxAttrSize to something more
reasonable (given what it's used for, namely checking char(n) declarations,
I didn't make it the full 1G that it could theoretically be --- 10Mb
seemed a more reasonable number). Improve calculation of MaxTupleSize.
|
|
CVs: ----------------------------------------------------------------------
|
|
|
|
are allowed in the func_name production. Otherwise, we can't define
more like() and ilike() functions for new data types.
|
|
If the backslash default is still wanted, just pass a backslash
to MatchText() for the two-parameter callable routines.
|
|
|
|
|
|
that RAND_MAX applies to them, since it doesn't. Instead add a
config.h parameter MAX_RANDOM_VALUE. This is currently set at 2^31-1
but could be auto-configured if that ever proves necessary. Also fix
some outright bugs like calling srand() where srandom() is appropriate.
|
