git.postgresql.org Git - postgresql.git/log
Fix misspellings of GB.
Correct misspellings of kB.
Cosmetic release note fix.
update for rc1
Copy fsync() defines into test_fsync.c, someday place them in an
include.
Propery align for O_DIRECT.
Check for write()/fsync() failures.
Document that to_char() "TM" is controlled by lc_messages.
Tom Lane [2006年11月24日 23:31:55 +0000 (23:31 +0000)]
Update release notes for RC1.
Tom Lane [2006年11月24日 23:06:50 +0000 (23:06 +0000)]
Fix psql's \copy command to ensure that it cycles libpq back to the idle state
(in particular, causing the ReadyForQuery message to be eaten) before
returning from do_copy. The only known consequence of failing to do so is
that get_prompt might show a wrong result for the %x transaction status
escape, as reported by Bernd Helmle; but it's possible there are other issues.
Back-patch as far as 7.4, the oldest version supporting %x.
Revert (too late in beta):
Fix to_char() locale handling to honor LC_TIME, not LC_MESSAGES.
Euler Taveira de Oliveira
Tom Lane [2006年11月24日 21:18:42 +0000 (21:18 +0000)]
Change pg_stat_all_tables and sister views to put the recently-added
vacuum/analyze timestamp columns at the end, rather than at a random
spot in the middle as in the original patch. This was deemed more usable
as well as less likely to break existing application code. initdb forced
accordingly. In passing, remove former kluge for initializing
pg_stat_file()'s pg_proc entry --- bootstrap mode was fixed recently
so that this can be done without any hacks, but I overlooked this usage.
Tom Lane [2006年11月24日 18:44:37 +0000 (18:44 +0000)]
Make contrib/isn pass the opr_sanity sanity checks: add missing
commutator operators, and mark hash-opclass members as oprcanhash.
This is a pretty ugly, brute-force solution, but it seems that getting
rid of all these redundant-looking operators would require some tweaks
in the core operator-resolution code to behave nicely, and I'm not
willing to risk that just before RC1.
Translation updates
Separate release preparation jobs for all releases and for major releases
Fix to_char() locale handling to honor LC_TIME, not LC_MESSAGES.
Euler Taveira de Oliveira
KB -> kB
Fix lowercasing while parse OO dictionary
Revert out:
Update fsync test to match new O_DIRECT behavior.
Greg Smith
Update fsync test to match new O_DIRECT behavior.
Greg Smith
Update wording:
> * Add a field 'isoyear' to extract(), based on the ISO week
Spelling and related minor fixes for the GIN docs.
Tom Lane [2006年11月23日 05:47:48 +0000 (05:47 +0000)]
Un-break ecpg regression test.
More minor SGML improvements for xfunc.sgml, including making some
titles more concise. (We usually don't need to repeat the name of a
section in the title of one of its subsections.)
Document that Kerberos is for authentication, and does not encrypt data
or queries over the network.
Fix a typo in recent xfunc addition, do some routine SGML police work.
Add a comment noting that heap_copytuple_with_tuple() results in a
HeapTuple that is no longer allocated as a single palloc() block; if
used carelessly, this might result in a subsequent memory leak after
heap_freetuple().
Update lock comments for concurrent index creation, analyze.
Walter Cruz
Add:
> * Add ISO day of week format 'ID' to to_char() where Monday = 1
> * Add an ISO year field to extract() called 'isoyear'
Add:
> * Allow SQL-language functions to return results from RETURNING queries
Make ecpg test variable 'times' static so as not to conflict with libc
symbol.
Add "(assuming <varname>standard_conforming_strings</> is
<literal>off</>)" clauses for bytea.
Shared Memory Hooks Documentation
This patch, against xfunc.sgml, adds a new subsection 33.9.12, Shared
Memory and LWLocks in C-Language Functions, describing how shared memory
and lwlocks may be requested by C add-in functions.
Marc Munro
Add release entry for 8.1.5 that was missing:
<listitem><para>Fix rare bug in continuous archiving (Tom)</para></listitem>
Tom Lane [2006年11月23日 01:14:59 +0000 (01:14 +0000)]
Several changes to reduce the probability of running out of memory during
AbortTransaction, which would lead to recursion and eventual PANIC exit
as illustrated in recent report from Jeff Davis. First, in xact.c create
a special dedicated memory context for AbortTransaction to run in. This
solves the problem as long as AbortTransaction doesn't need more than 32K
(or whatever other size we create the context with). But in corner cases
it might. Second, in trigger.c arrange to keep pending after-trigger event
records in separate contexts that can be freed near the beginning of
AbortTransaction, rather than having them persist until CleanupTransaction
as before. Third, in portalmem.c arrange to free executor state data
earlier as well. These two changes should result in backing off the
out-of-memory condition before AbortTransaction needs any significant
amount of memory, at least in typical cases such as memory overrun due
to too many trigger events or too big an executor hash table. And all
the same for subtransaction abort too, of course.
More HA wording improvements.
Update HA docs with more wording improvements.
Wording and term clarification for HA docs, per Markus Schiltknecht.
Avoid infinity calculations in rank_cd
Mention OIDs are now not created by default.
New async/sync multi-master headings for docs.
New async/sync multi-master headings for docs.
Add mention of shared-memory/disk for multi-master clustering.
Tom Lane [2006年11月21日 23:26:47 +0000 (23:26 +0000)]
Get rid of retail definitions of HAVE_STRDUP and HAVE_VSNPRINTF in
some of the Windows-only makefiles; the correct place to assert these
things is pg_config.h.win32. Per bug #2677.
Tom Lane [2006年11月21日 23:11:55 +0000 (23:11 +0000)]
Translate Windows' GMT Standard Time/GMT Daylight Time zones to
zic's Europe/London, rather than Europe/Dublin as before. This seems
a less surprising choice, particularly with respect to dates before
1948. Original suggestion was to translate to straight GMT, but this
seems wrong given that these zones *are* DST-aware. Per offlist
discussion with Magnus.
HA doc wording improvement.
Tom Lane [2006年11月21日 22:35:29 +0000 (22:35 +0000)]
Prevent intratransaction memory leak when a subtransaction is aborted
in the middle of executing a SPI query. This doesn't entirely fix the
problem of memory leakage in plpgsql exception handling, but it should
get rid of the lion's share of leakage.
Tom Lane [2006年11月21日 22:19:46 +0000 (22:19 +0000)]
Suppress timezone (%Z) part of timestamp display when running on Windows,
because on that platform strftime produces localized zone names in varying
encodings. Even though it's only in a comment, this can cause encoding
errors when reloading the dump script. Per suggestion from Andreas
Seltenreich. Also, suppress %Z on Windows in the %s escape of
log_line_prefix ... not sure why this one is different from the other two,
but it shouldn't be.
Tom Lane [2006年11月21日 21:51:05 +0000 (21:51 +0000)]
Fix plpython to work (or at least pass its regression tests) with
python 2.5. This involves fixing several violations of the published
spec for creating PyTypeObjects, and adding another regression test
expected output for yet another variation of error message spelling.
Mention pgpool-II can do Clustering For Parallel Query Execution.
Tom Lane [2006年11月21日 20:59:53 +0000 (20:59 +0000)]
On systems that have setsid(2) (which should be just about everything except
Windows), arrange for each postmaster child process to be its own process
group leader, and deliver signals SIGINT, SIGTERM, SIGQUIT to the whole
process group not only the direct child process. This provides saner behavior
for archive and recovery scripts; in particular, it's possible to shut down a
warm-standby recovery server using "pg_ctl stop -m immediate", since delivery
of SIGQUIT to the startup subprocess will result in killing the waiting
recovery_command. Also, this makes Query Cancel and statement_timeout apply
to scripts being run from backends via system(). (There is no support in the
core backend for that, but it's widely done using untrusted PLs.) Per gripe
from Stephen Harris and subsequent discussion.
Update Statement-Based Replication Middleware docs to be more general.
Fix type in return value
In HA/load balancing does:
Clarify sync/async replication propogation delay issues.
Add SGML comment about Oracle RAC and remove doc mention.
Add item about Multi-master replication with conflict resolution.
VC build patch from Magnus:
Typo in the changes to plperl - uses wrong dir, and had a missing slash.
Also fixes error checking for xsubpp - it was broken in a way that hid
the problem above when run more than once (which is the normal case when
developing).
Move libpq environment reference in psql documentation to a more
appropriate place, per Andrew Dunstan.
remove duplicate declaration, per report from Magnus Hagander.
Tom Lane [2006年11月21日 16:28:00 +0000 (16:28 +0000)]
If SSL negotiation fails and SSLMODE is 'prefer', then retry without SSL.
Negotiation failure is only likely to happen if one side or the other is
misconfigured, eg. bad client certificate. I'm not 100% convinced that
a retry is really the best thing, hence not back-patching this fix for now.
Per gripe from Sergio Cinos.
Add capitalization mention.
I noticed that the Partitioning section of the docs has *two* sections
of caveats in different places, but close together. One called caveats,
one not. That looks like it just led to somebody not reading some
appropriate caveats in the second group of caveats (on -admin).
Simon Riggs
Tom Lane [2006年11月21日 01:23:37 +0000 (01:23 +0000)]
Change the default setting for log_min_error_statement to ERROR. Per
recent discussion in which majority opinion was that this is a more
widely useful setting than the previous default of PANIC.
Tom Lane [2006年11月21日 00:49:55 +0000 (00:49 +0000)]
Adjust elog.c so that elog(FATAL) exits (including cases where ERROR is
promoted to FATAL) end in exit(1) not exit(0). Then change the postmaster to
allow exit(1) without a system-wide panic, but not for the startup subprocess
or the bgwriter. There were a couple of places that were using exit(1) to
deliberately force a system-wide panic; adjust these to be exit(2) instead.
This fixes the problem noted back in July that if the startup process exits
with elog(ERROR), the postmaster would think everything is hunky-dory and
proceed to start up. Alternative solutions such as trying to run the entire
startup process as a critical section seem less clean, primarily because of
the fact that a fair amount of startup code is shared by all postmaster
children in the EXEC_BACKEND case. We'd need an ugly special case somewhere
near the head of main.c to make it work if it's the child process's
responsibility to determine what happens; and what's the point when the
postmaster already treats different children differently?
Retitle documentation section, "Statement-Based Replication Using Middleware".
Add mention that Shared Disk Failover can use file system mirroring of
the mirroring is consistent.
Update Brazilian FAQ.
Euler Taveira de Oliveira
For to_char() day/month abbrevitions, mention "3 chars in English,
localized lengths vary".
Our MingW FAQ appears to be seriously out of date. Couple of fixes: we
want to direct MSI downloads to main download site, NT4 not supported
anymore, msvc build env in progress, pgsql-hackers-win32 is no more.
Magnus Hagander
Tom Lane [2006年11月20日 19:18:02 +0000 (19:18 +0000)]
More MSVC build fixes:
* New versions of OpenSSL come with proper debug versions, and use
suffixed names on the LIBs for that. Adapts library handling to deal
with that.
* Fixes error where it incorrectly enabled Kerberos based on NLS
configuration instead of Kerberos configuration
* Specifies path of perl in config, instead of using current one.
Required when using a 64-bit perl normally, but want to build pl/perl
against 32-bit one (required)
* Fix so pgevent generates win32ver.rc automatically
Magnus Hagander
Overhaul the "External Projects" chapter in the manual. Replace
the variabelist with a more concise table, add a URL for each project,
remove some orphaned projects, add PL/Py, and various other changes.
Initial patch from Robert Treat, subsequent work by Neil Conway.
Update documentation to use Statement-Based Replication rather than
Query Broadcast.
Fix bug archives.postgresql.org/pgsql-bugs/2006-10/msg00258.php.
Fix string's length calculation for recoding, fix strlower() to avoid wrong
assumption about length of recoded string (was: recoded string is no greater
that source, it may not true for multibyte encodings)
Thanks to Thomas H. <me@alternize.com> and Magnus Hagander <mha@sollentuna.net>
Tom Lane [2006年11月20日 01:07:56 +0000 (01:07 +0000)]
When truncating a relation in-place (eg during VACUUM), do not try to unlink
any no-longer-needed segments; just truncate them to zero bytes and leave
the files in place for possible future re-use. This avoids problems when
the segments are re-used due to relation growth shortly after truncation.
Before, the bgwriter, and possibly other backends, could still be holding
open file references to the old segment files, and would write dirty blocks
into those files where they'd disappear from the view of other processes.
Back-patch as far as 8.0. I believe the 7.x branches are not vulnerable,
because they had no bgwriter, and "blind" writes by other backends would
always be done via freshly-opened file references.
Tom Lane [2006年11月19日 21:33:23 +0000 (21:33 +0000)]
Repair problems with hash indexes that span multiple segments: the hash code's
preference for filling pages out-of-order tends to confuse the sanity checks
in md.c, as per report from Balazs Nagy in bug #2737. The fix is to ensure
that the smgr-level code always has the same idea of the logical EOF as the
hash index code does, by using ReadBuffer(P_NEW) where we are adding a single
page to the end of the index, and using smgrextend() to reserve a large batch
of pages when creating a new splitpoint. The patch is a bit ugly because it
avoids making any changes in md.c, which seems the most prudent approach for a
backpatchable beta-period fix. After 8.3 development opens, I'll take a look
at a cleaner but more invasive patch, in particular getting rid of the now
unnecessary hack to allow reading beyond EOF in mdread().
Backpatch as far as 7.4. The bug likely exists in 7.3 as well, but because
of the magnitude of the 7.3-to-7.4 changes in hash, the later-version patch
doesn't even begin to apply. Given the other known bugs in the 7.3-era hash
code, it does not seem worth trying to develop a separate patch for 7.3.
Tom Lane [2006年11月17日 23:25:17 +0000 (23:25 +0000)]
Clarify description of CIDR-address column of pg_hba.conf, to discourage
people from trying notations like '10.6/16', which is accepted but does
not mean what you probably think. Per example from Paul Forgey.
Tom Lane [2006年11月17日 18:00:15 +0000 (18:00 +0000)]
Repair two related errors in heap_lock_tuple: it was failing to recognize
cases where we already hold the desired lock "indirectly", either via
membership in a MultiXact or because the lock was originally taken by a
different subtransaction of the current transaction. These cases must be
accounted for to avoid needless deadlocks and/or inappropriate replacement of
an exclusive lock with a shared lock. Per report from Clarence Gardner and
subsequent investigation.
Small message equalization fix
Rename replication section "High Availability and Load Balancing".
Data Partitioning documentation section reduced and moved to the end.
Fix a typo.
Fixed small typo, missing 'l' in 'Cluserting'
Remove a bunch of antique information from the appendix in the docs
that discusses CVS. Remove the recommendation to use cvs 1.10. Remove
discussion of alleged CVSup binaries on postgresql.org, because they
have not existed for several years. Remove discussion of how to
build cvsup from source because the existing text is outdated, and
more accurate information is available from the CVSup homepage.
Use more standard terms for replication, ideas from Markus Schiltknecht.
Mention two-phase commit for having all transactions commit on all servers.
Reconfigure failover/replication doc items to be varlist entries, rather
than new sections, so they appear all on the same web page.
Clarify replication items, and define some terms.
Message fix
String fix
Improve broadcast wording for failover/clustering documentation.
Add URL for case identifiers.
<
> http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php
Fix xrefs for failover changes.
Update failover docs, per suggestions from Chris Browne.
Fix URL for patch hold queue.
Force plperl and plperlu to run in separate interpreters. Create an error
on an attempt to create the second interpreter if this is not supported by
the perl installation. Per recent -hackers discussion.
Fix some typos in comments.
Do a round of copy-editing for the system catalog chapter. In particular,
consistently capitalize the content of the "Description" column but do
not include a terminating period, as is the convention elsewhere in the
docs. Also, remove the "References" column from catalog that do not
have any referencing columns, for the sake of brevity. Make various
other SGML and grammar fixes.
Minor improvements to the description of archive_timeout.
Tom Lane [2006年11月11日 01:14:19 +0000 (01:14 +0000)]
Suppress a few 'uninitialized variable' warnings that gcc emits only at
-O3 or higher (presumably because it inlines more things). Per gripe
from Mark Mielke.
Tom Lane [2006年11月10日 22:59:29 +0000 (22:59 +0000)]
Fix pg_get_serial_sequence(), which could incorrectly return the name
of an index on a serial column, rather than the name of the associated
sequence. Fallout from recent changes in dependency setup for serials.
Per bug #2732 from Basil Evseenko.
Tom Lane [2006年11月10日 22:32:20 +0000 (22:32 +0000)]
Clean up some misleading references to %p being a full path, per Simon.
Tom Lane [2006年11月10日 22:15:26 +0000 (22:15 +0000)]
Improve formatting of PQexecParams argument descriptions, per
Theo Kramer.
Tom Lane [2006年11月10日 20:52:18 +0000 (20:52 +0000)]
Emphasize that immutable and stable functions are not allowed to modify
the database. xfunc.sgml was already pretty definite on the point, but
it doesn't hurt to make it clear here too.
Tom Lane [2006年11月10日 18:10:10 +0000 (18:10 +0000)]
Fix errors in key_column_usage.position_in_unique_constraint column recently
added to information_schema (per a SQL2003 addition). The original coding
failed if a referenced column participated in more than one pg_constraint
entry. Also, it did not work if an FK relied directly on a unique index
without any constraint syntactic sugar --- this case is outside the SQL spec,
but PG has always supported it, so it's reasonable for our information_schema
to handle it too. Per bug#2750 from Stephen Haberman.
Although this patch changes the initial catalog contents, I didn't force
initdb. Any beta3 testers who need the fix can install it via CREATE OR
REPLACE VIEW, so forcing them to initdb seems an unnecessary imposition.
This is the main PostgreSQL git repository.
RSS
Atom