| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
absolute paths of the source tree in the po files. Also, run msgfmt with
-c option in maintainer-check.
|
| |
|
|
|
|
| |
* Make n of CHAR(n)/VARCHAR(n) the number of letters, not bytes
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
null terminated strings. The FE/BE protocol sends in some cases null
terminated strings to the client. The docs for the FE/BE protocol state
that there is no limit on the size of a null terminated string sent to
the client and a client should be coded using an expanding buffer to
deal with large strings. The old code did not do this and gave an error
if a null terminated string was greater than either 4 or 8K. It appears
that with the advent of TOAST very long SQL statements are becoming more
common, and apparently some error messages from the backend include the
SQL statement thus easily exceeding the 8K limit in the old code.
In fixing I also cleaned up some calls in the JDBC fastpath code that
were not doing character set conversion under multibyte, and removed
some methods that were no longer needed. I also removed a potential
threading problem with a shared variable that was being used in
Connection.java.
Thanks to Steve Wampler for discovering the problem and sending the
initial diffs that were the basis of this patch.
thanks,
--Barry
|
|
|
|
|
| |
because index locking issues are not handled correctly yet. Need to go
work on the index AMs next.
|
| |
|
| |
|
|
|
|
| |
From Vince Vielhaber.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
validity checking rules for VACUUM. Make some other rearrangements of the
VACUUM code to allow more code to be shared between full and lazy VACUUM.
Minor code cleanups and added comments for TransactionId manipulations.
|
| |
|
|
|
|
|
|
| |
> > for docs, hope he does not mind ;)
Marko Kreen
|
|
|
|
| |
Christian Ullrich
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
a lie on many Unixen), invoke listen() with MIN(MaxBackends*2, 10000).
The clamp value 10000 is configurable in config.h.in, if that proves
to be necessary --- hopefully it won't.
|
|
|
|
|
|
|
| |
terminology. Also, the function owner is now determined and saved at compile
time (no gotchas here, right?)/
Mark Volpe
|
|
|
|
|
|
|
| |
This makes VACUUM work properly with partial indexes, and avoids memory
leakage with functional indexes. Also, suppress complaint about fewer
index tuples than heap tuples when the index is a partial index.
From Martijn van Oosterhout.
|
|
|
|
|
|
| |
INITIALLY DEFERRED in source code. cf. preproc.y:1455.
Unknown.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
USER and ALTER USER to appear in any order, not only the fixed order
they used to be required to appear in.
Also, some changes from Tom Lane to create a FULL option for VACUUM;
it doesn't do anything yet, but I needed to change many of the same
files to make that happen, so now seemed like a good time.
|
|
|
|
|
|
| |
choice of compiler and flags, uninstall, and peculiar Python installation
layouts for PyGreSql. Also install into site-packages now, as officially
recommended. And pgdb.py is also installed now, used to be forgotten.
|
|
|
|
|
| |
Enforce MAXTZLEN for all datestyles, not just some. Remove macro
definitions that were redundant with datetime.h.
|
| |
|
|
|
|
| |
IS NULL, IS TRUE, and friends (my fault...)
|
|
|
|
|
|
| |
in cases of qualified rules as well as unqualified ones. Tweak rules
test to avoid cluttering output with dummy SELECT results. Update
documentation to match code.
|
|
|
|
| |
Name chosen per pghackers discussion around 6/22/01.
|
| |
|
| |
|
|
|
|
| |
postgresql.res.badint, since that's the name in the properties file.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* NULLs are sorted differently in 7.2
* table correlation names are supported
* GROUP BY, ORDER BY unrelated is supported since 6.4
* ESCAPE/LIKE only supported since 7.1
* outer joins only since 7.1
* preferred term for procedure is "function"
* preferred term for catalog is "database"
* supports SELECT for UPDATE since 6.5
* supports subqueries
* supports UNION; supports UNION ALL since 7.1
* update some of the max lengths to match reality
* rearrange some functions to match the order in the spec
for easier maintenance
|
| |
|
|
|
|
|
|
|
|
|
| |
redirections between the build files, which didn't work completely. Now
you just go to the directory of your choice and run make. Clean up the
build files to have a logical order, fix the unnecessary rebuilds, prevent
the deleting targets from removing files they're not responsible for. Ant
1.3 does not have a bug. It deletes directories just fine if you follow
the documentation.
|
|
|
|
|
| |
to wait until it's safe to remove tuples and compact free space in a
shared buffer page. Miscellaneous small code cleanups in bufmgr, too.
|
| |
|
| |
|
|
|
|
|
| |
the startup exchange is complete. Also make sure that packets defined as
single bytes aren't sent with a trailing '\0'.
|
|
|
|
| |
Jan
|
| |
|
|
|
|
|
| |
not holding a pin on the page. Use double instead of long to count
rows in relation, so that code still works for > LONG_MAX rows in rel.
|
|
|
|
| |
Jan
|
|
|
|
|
|
|
|
|
|
| |
constraint. This case (a) is useless, (b) violates SQL92, and
(c) is certain to cause a failure downstream when we try to create
an index with duplicated column names. So give an appropriate error
message instead of letting the index failure occur. Per report from
Colin Strickland. NOTE: currently, CREATE INDEX fooi ON foo(f1,f1)
still fails with 'cannot insert duplicate key' error. Should we
change that too? What about functional indexes?
|
| |
|