git.postgresql.org Git - postgresql.git/log
Add:
> * Allow WAL replay of CREATE TABLESPACE to work when the directory
> structure on the recovery computer is different from the original
Add:
> o Update pg_dump and psql to use the new COPY libpq API
Remove:
< o Update to use the newer COPY syntax
Add for pg_dump:
> o Update to use the newer COPY syntax
Add:
>
> * Support table partitioning that allows a single table to be stored
> in subtables that are partitioned based on the primary key or a WHERE
> clause
Remove:
<
< o Prevent conflicting SET options from being set
<
< This requires a checking function to be called after the server
< configuration file is read.
Tom Lane [2005年3月23日 00:03:37 +0000 (00:03 +0000)]
WAL must log CREATE and DROP DATABASE operations *without* using any
explicit paths, so that the log can be replayed in a data directory
with a different absolute path than the original had. To avoid forcing
initdb in the 8.0 branch, continue to accept the old WAL log record
types; they will never again be generated however, and the code can be
dropped after the next forced initdb. Per report from Oleg Bartunov.
We still need to think about what it really means to WAL-log CREATE
TABLESPACE commands: we more or less have to put the absolute path
into those, but how to replay in a different context??
Tom Lane [2005年3月22日 20:13:09 +0000 (20:13 +0000)]
Use InitFunctionCallInfoData() macro instead of MemSet in performance
critical places in execQual. By Atsushi Ogawa; some minor cleanup by moi.
Tom Lane [2005年3月22日 06:17:03 +0000 (06:17 +0000)]
Create a routine PageIndexMultiDelete() that replaces a loop around
PageIndexTupleDelete() with a single pass of compactification ---
logic mostly lifted from PageRepairFragmentation. I noticed while
profiling that a VACUUM that's cleaning up a whole lot of deleted
tuples would spend as much as a third of its CPU time in
PageIndexTupleDelete; not too surprising considering the loop method
was roughly O(N^2) in the number of tuples involved.
Tom Lane [2005年3月21日 16:29:20 +0000 (16:29 +0000)]
Fix quote_ident to use quote_identifier rather than its own, not quite
up-to-speed logic; in particular this will cause it to quote names that
match keywords. Remove unnecessary multibyte cruft from quote_literal
(all backend-internal encodings are 8-bit-safe).
pgcrypto update:
* test error handling
* add tests for des, 3des, cast5
* add some tests to blowfish, rijndael
* Makefile: ability to specify different tests for different crypto
libraries, so we can skip des, 3des and cast5 for builtin.
Marko Kreen
pgcrypto update:
Reserve px_get_random_bytes() for strong randomness,
add new function px_get_pseudo_random_bytes() for
weak randomness and use it in gen_salt().
On openssl case, use RAND_pseudo_bytes() for
px_get_pseudo_random_bytes().
Final result is that is user has not configured random
souce but kept the 'silly' one, gen_salt() keeps
working, but pgp_encrypt() will throw error.
Marko Kreen
pgcrypto update:
* openssl.c: Add 3des and AES support
* README.pgcrypto: list only supported ciphers for openssl
OpenSSL has pre-processor symbol OPENSSL_NO_AES, which
isn't that helpful for detecting if it _does_ exist.
Thus the hack with AES_ENCRYPT.
Marko Kreen
pgcrypto update:
* Use error codes instead of -1
* px_strerror for new error codes
* calling convention change for px_gen_salt - return error code
* use px_strerror in pgcrypto.c
Marko Kreen
* construct "struct {} list [] = {}" confuses pgindent - split those.
It was a bad style to begin with, and now several loops can be clearer.
* pgcrypto.c: Fix function comments
* crypt-gensalt.c, crypt-blowfish.c: stop messing with errno
* openssl.c: use px_free instead pfree
* px.h: make redefining px_alloc/px_realloc/px_free easier
Marko Kreen
Remove support for libmhash/libmcrypt.
libmcrypt seems to dead, maintainer address bounces,
and cast-128 fails on 2 of the 3 test vectors from RFC2144.
So I see no reason to keep around stuff I don't trust
anymore.
Support for several crypto libraries is probably only
confusing to users, although it was good for initial
developing - it helped to find hidden assumptions and
forced me to create regression tests for all functionality.
Marko Kreen
Tom Lane [2005年3月21日 01:24:04 +0000 (01:24 +0000)]
Convert index-related tuple handling routines from char 'n'/' ' to bool
convention for isnull flags. Also, remove the useless InsertIndexResult
return struct from index AM aminsert calls --- there is no reason for
the caller to know where in the index the tuple was inserted, and we
were wasting a palloc cycle per insert to deliver this uninteresting
value (plus nontrivial complexity in some AMs).
I forced initdb because of the change in the signature of the aminsert
routines, even though nothing really looks at those pg_proc entries...
Change the return value of HeapTupleSatisfiesUpdate() to be an enum,
rather than an integer, and fix the associated fallout. From Alvaro
Herrera.
Tom Lane [2005年3月20日 22:27:52 +0000 (22:27 +0000)]
On Windows, use QueryPerformanceCounter instead of gettimeofday for
EXPLAIN ANALYZE instrumentation. Magnus Hagander
Tom Lane [2005年3月20日 22:00:54 +0000 (22:00 +0000)]
Remove unnecessary calls of FlushRelationBuffers: there is no need
to write out data that we are about to tell the filesystem to drop.
smgr_internal_unlink already had a DropRelFileNodeBuffers call to
get rid of dead buffers without a write after it's no longer possible
to roll back the deleting transaction. Adding a similar call in
smgrtruncate simplifies callers and makes the overall division of
labor clearer. This patch removes the former behavior that VACUUM
would write all dirty buffers of a relation unconditionally.
Add mention of why malloc() has to be used in snprintf.c.
Department of second thoughts. Remove FRONTEND from snprintf.c because
snprintf is called before the memory system is started. We have to just
malloc/free. There are no elogs in the code so we should be fine.
Fix typo in Makefile.
Another change for FRONTEND snprintf.c.
Mark snprintf.c as a file that uses FRONTEND and needs to a version in
the server-side port library. Somehow I missed that change when I added
memory allocation to snprintf.c.
Done:
> * -Allow the size of the buffer cache used by temporary objects to be
Tom Lane [2005年3月19日 23:27:11 +0000 (23:27 +0000)]
Add temp_buffers GUC variable to allow users to determine the size
of the local buffer arena for temporary table access.
Tom Lane [2005年3月19日 17:39:43 +0000 (17:39 +0000)]
Upgrade localbuf.c to use a hash table instead of linear search to
find already-allocated local buffers. This is the last obstacle
in the way of setting NLocBuffer to something reasonably large.
Tom Lane [2005年3月18日 17:32:55 +0000 (17:32 +0000)]
Put 'dump complete' message in the right place, so it comes out where
it's supposed to when --file option is used.
Tom Lane [2005年3月18日 16:16:09 +0000 (16:16 +0000)]
Need to reset local buffer pin counts, not only shared buffer pins,
before we attempt any file deletions in ShutdownPostgres. Per Tatsuo.
Added patch by Christof Petig <christof@petig-baender.de> to work around gcc bug on powerpc and amd64.
Tom Lane [2005年3月18日 05:25:23 +0000 (05:25 +0000)]
Avoid infinite loop in InvalidateBuffer if we ourselves are holding
a pin on the victim buffer.
Tom Lane [2005年3月18日 05:24:13 +0000 (05:24 +0000)]
Need to release buffer pins before attempting to drop files during
backend exit. Per report from Bruce.
Tom Lane [2005年3月18日 03:48:49 +0000 (03:48 +0000)]
Treat EPERM as a non-error case when checking to see if old postmaster
is still alive. This improves our odds of not getting fooled by an
unrelated process when checking a stale lock file. Other checks already
in place, plus one newly added in checkDataDir(), ensure that we cannot
attempt to usurp the place of a postmaster belonging to a different userid,
so there is no need to error out. Add comments indicating the importance
of these other checks.
This patch moves some code for preprocessing FOR UPDATE from
grouping_planner() to preprocess_targetlist(), according to a comment
in grouping_planner(). I think the refactoring makes sense, and moves
some extraneous details out of grouping_planner().
Add link to INSERT in docs.
Robert Treat
Update file system snapshot docs.
Tom Lane [2005年3月17日 15:25:51 +0000 (15:25 +0000)]
Update obsolete comment.
Trivial comment tweak.
Mention tablespaces as a problem for using file system snapshots.
Document use of rsync for file system backups.
Tino Wildenhain
Add mention of compatibility problem with turning off backslash escapes:
< SQL-spec compliant, so allow such handling to be disabled.
> SQL-spec compliant, so allow such handling to be disabled. However,
> disabling backslashes could break many third-party applications and tools.
Factor duplicate snprintf code into functions.
Add a reference to the documentation on alternate index operator classes in
the locale docs. Patch from Chris KL, editorialization by Neil Conway.
This patch makes \d on tables and views sort fk constraints, triggers
and rules alphabetically in the output. This makes it the same as
for indexes and stops the irritating random or reverse ordering it
currently has.
Chris KL
Force initdb cause of encoding additions.
Tom Lane [2005年3月16日 21:38:10 +0000 (21:38 +0000)]
Revise TupleTableSlot code to avoid unnecessary construction and disassembly
of tuples when passing data up through multiple plan nodes. A slot can now
hold either a normal "physical" HeapTuple, or a "virtual" tuple consisting
of Datum/isnull arrays. Upper plan levels can usually just copy the Datum
arrays, avoiding heap_formtuple() and possible subsequent nocachegetattr()
calls to extract the data again. This work extends Atsushi Ogawa's earlier
patch, which provided the key idea of adding Datum arrays to TupleTableSlots.
(I believe however that something like this was foreseen way back in Berkeley
days --- see the old comment on ExecProject.) A test case involving many
levels of join of fairly wide tables (about 80 columns altogether) showed
about 3x overall speedup, though simple queries will probably not be
helped very much.
I have also duplicated some code in heaptuple.c in order to provide versions
of heap_formtuple and friends that use "bool" arrays to indicate null
attributes, instead of the old convention of "char" arrays containing either
'n' or ' '. This provides a better match to the convention used by
ExecEvalExpr. While I have not made a concerted effort to get rid of uses
of the old routines, I think they should be deprecated and eventually removed.
Add sprintf support, that were were missing.
Add support for snprintf '+', 'h', and %* length settings.
pgindent snprintf.c for consistency.
Fix snprintf for %*$.
Add CVS \r\n regression tests.
Andrew Dunstan
Fix snprintf to handle %$ properly by storing and reordering the
arguments.
Nicolai Tufar
Add missing include for new lc_ctype_is_c() function.
Per Neil.
Prevent locale-aware handling of upper, lower, and initcap when the
locale is C.
Backpatch to 8.0.X because some operating systems were throwing errors
for such operations, rather than ignoring the locale when it was C.
Wrap the implementation of fork_process() inside #ifndef WIN32 -- this
should hopefully unbreak the Win32 build. Apologies for breaking it in
the first place.
Update to 8.0.1.
Add:
> * Allow sequential scans to take advantage of other concurrent
> sequentiqal scans, also called "Synchronised Scanning"
Update Win32 item:
< o Disallow encodings like UTF8 which PostgreSQL supports
< but the operating system does not (already disallowed by
< pginstaller)
> o Add support for Unicode
< To fix UTF8, the data needs to be converted to UTF16 and then
< the Win32 wcscoll() can be used, and perhaps other functions
> To fix this, the data needs to be converted to/from UTF16/UTF8
> so the Win32 wcscoll() can be used, and perhaps other functions
< locales but provides no ordering.
<
> locales but provides no ordering or character set classes.
Clean up win1252 documentation. Mention how we determine the number of
bytes/character for each encoding.
Issue free space notices to both the user and the server log file.
Tom Lane [2005年3月14日 18:57:33 +0000 (18:57 +0000)]
Make pg_dump emit a useful error message, instead of just dumping core,
if it finds a pg_rewrite entry for which there is no pg_class entry.
Per report from Andrew Slobodyanyk.
Add support for Win1252 encoding.
Roland Volkmann
Bump minor version numbers for 8.1 compared to 8.0.
Completed:
> * -Cache last known per-tuple offsets to speed long tuple access
Fix mistakes in SGML markup. From David Fetter.
Tom Lane [2005年3月14日 06:19:01 +0000 (06:19 +0000)]
Note that the -F and -R command line options only affect unaligned
output mode. This was already stated in other places in the psql
reference page, but not here.
Tom Lane [2005年3月14日 04:41:13 +0000 (04:41 +0000)]
Avoid O(N^2) overhead in repeated nocachegetattr calls when columns of
a tuple are being accessed via ExecEvalVar and the attcacheoff shortcut
isn't usable (due to nulls and/or varlena columns). To do this, cache
Datums extracted from a tuple in the associated TupleTableSlot.
Also some code cleanup in and around the TupleTable handling.
Atsushi Ogawa with some kibitzing by Tom Lane.
Document client-only encodings.
Fix typo on URL.
Add user:
> * Support triggers on columns (Greg Sabino Mullane)
Finalize character set documentation changes.
Allow ALTER FUNCTION to change a function's strictness, volatility, and
whether or not it is a security definer. Changing a function's strictness
is required by SQL2003, and the other capabilities make sense. Also, allow
an optional RESTRICT noise word to be specified, for SQL conformance.
Some trivial regression tests added and the documentation has been
updated.
Update comments for new encoding names.
Tom Lane [2005年3月13日 23:32:26 +0000 (23:32 +0000)]
Add missing identification comment, remove entirely inappropriate include
of postgres.h.
Tom Lane [2005年3月13日 23:27:38 +0000 (23:27 +0000)]
Add some missing #includes.
Increment all major version numbers in 8.0.X to force recompile of
client aplications so 7.4.X releases can be installed on the same
machine as 8.0.X.
Tom Lane [2005年3月13日 19:59:40 +0000 (19:59 +0000)]
Forgot that I had intended to replace division by masking in hash calculation.
Remove CENTER tag.
Make default_with_oids default to false -- user-created tables will now
no longer include OIDs, unless WITH OIDS is specified or the
default_with_oids configuration parameter is enabled. Update the docs
accordingly.
More ordering adjustments.
Update obsolete comment.
Fix markup.
More markup changes.
More cleanups.
More improvements.
More additions to the table.
Keep changing the markup until I like it. :-)
More table markup improvements.
More table markup fixes.
Rework "aliases" column for encodings.
Fix markup typo.
Add missing conversion documentation for certain encodings.
Reorder documented encodings to be alphabetical.
Remove warning about pre-7.2 LATIN5 usage.
Document aliases for our supported encodings.
Add a few encodings that were not documented.
Tom Lane [2005年3月12日 21:33:55 +0000 (21:33 +0000)]
When cloning template0 (or other fully-frozen databases), set the new
database's datallowconn and datfrozenxid to the current transaction ID
instead of copying the source database's values. This is OK because we
assume the source DB contains no normal transaction IDs whatsoever.
This keeps VACUUM from immediately starting to complain about unvacuumed
databases in the situation where we are more than 2 billion transactions
out from the XID stamp of template0. Per discussion with Milen Radev
(although his complaint turned out to be due to something else, but the
problem is real anyway).
Tom Lane [2005年3月12日 21:11:50 +0000 (21:11 +0000)]
Fix ALTER DATABASE RENAME to allow the operation if user is a superuser
who for some reason isn't marked usecreatedb. Per report from Alexander
Pravking. Also fix sloppy coding in have_createdb_privilege().
Tom Lane [2005年3月12日 20:25:06 +0000 (20:25 +0000)]
Adjust the API for aggregate function calls so that a C-coded function
can tell whether it is being used as an aggregate or not. This allows
such a function to avoid re-pallocing a pass-by-reference transition
value; normally it would be unsafe for a function to scribble on an input,
but in the aggregate case it's safe to reuse the old transition value.
Make int8inc() do this. This gets a useful improvement in the speed of
COUNT(*), at least on narrow tables (it seems to be swamped by I/O when
the table rows are wide). Per a discussion in early December with
Neil Conway. I also fixed int_aggregate.c to check this, thereby
turning it into something approaching a supportable technique instead
of being a crude hack.
Add pg_buffercache contrib module, from Mark Kirkwood.
Some builds (depends on crypto engine support?) of OpenSSL
0.9.7x have EVP_DigestFinal function which which clears all of
EVP_MD_CTX. This makes pgcrypto crash in functions which
re-use one digest context several times: hmac() and crypt()
with md5 algorithm.
Following patch fixes it by carring the digest info around
EVP_DigestFinal and re-initializing cipher.
Marko Kreen.
Documention all our supported encodings.
This is the main PostgreSQL git repository.
RSS
Atom