Log Message:
---
Create 9.0 release notes; keep 9.0-alpha release notes in place.
Modified Files:
--
pgsql/doc/src/sgml:
release-9.0.sgml (r2.2 -> r2.3)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release-9.0.sgml?r1=2.2&r2=2.3)
--
Sent
Log Message:
---
Update sgml release note markup suggestions.
Modified Files:
--
pgsql/doc/src/sgml:
release.sgml (r1.635 -> r1.636)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml?r1=1.635&r2=1.636)
--
Sent via pgsql-committers
Log Message:
---
Clear error_context_stack and debug_query_string at the beginning of proc_exit,
so that we won't try to attach any context printouts to messages that get
emitted while exiting. Per report from Dennis Koegel, the context functions
won't necessarily work after we've started
Log Message:
---
Clear error_context_stack and debug_query_string at the beginning of proc_exit,
so that we won't try to attach any context printouts to messages that get
emitted while exiting. Per report from Dennis Koegel, the context functions
won't necessarily work after we've started
Log Message:
---
Clear error_context_stack and debug_query_string at the beginning of proc_exit,
so that we won't try to attach any context printouts to messages that get
emitted while exiting. Per report from Dennis Koegel, the context functions
won't necessarily work after we've started
Log Message:
---
Clear error_context_stack and debug_query_string at the beginning of proc_exit,
so that we won't try to attach any context printouts to messages that get
emitted while exiting. Per report from Dennis Koegel, the context functions
won't necessarily work after we've started
Log Message:
---
Clear error_context_stack and debug_query_string at the beginning of proc_exit,
so that we won't try to attach any context printouts to messages that get
emitted while exiting. Per report from Dennis Koegel, the context functions
won't necessarily work after we've started
Log Message:
---
Clear error_context_stack and debug_query_string at the beginning of proc_exit,
so that we won't try to attach any context printouts to messages that get
emitted while exiting. Per report from Dennis Koegel, the context functions
won't necessarily work after we've started
Log Message:
---
Clear error_context_stack and debug_query_string at the beginning of proc_exit,
so that we won't try to attach any context printouts to messages that get
emitted while exiting. Per report from Dennis Koegel, the context functions
won't necessarily work after we've started
Log Message:
---
Forbid renaming columns of objects whose column names are system-generated.
KaiGai Kohei, with adjustments to the comments.
Modified Files:
--
pgsql/src/backend/commands:
tablecmds.c (r1.328 -> r1.329)
(http://anoncvs.postgresql.org/cvsweb
Log Message:
---
Modify error context callback functions to not assume that they can fetch
catalog entries via SearchSysCache and related operations. Although, at the
time that these callbacks are called by elog.c, we have not officially aborted
the current transaction, it still seems rath
Log Message:
---
Modify error context callback functions to not assume that they can fetch
catalog entries via SearchSysCache and related operations. Although, at the
time that these callbacks are called by elog.c, we have not officially aborted
the current transaction, it still seems rath
Log Message:
---
Fix oversight in btpo.xact patch; it was in fact installing garbage
in the xact field on replay, due to not writing out all the data in
the wal log struct.
Modified Files:
--
pgsql/src/include/access:
nbtree.h (r1.131 -> r1.132)
(http://ano
Log Message:
---
Clarify docs about database parameter in streaming replication primary_conninfo.
Docs were unclear on whether or not database=replication was required,
nor did they mention the FATAL error this causes if database parameter is
mentioned explicitly, whatever its value.
Modif
Log Message:
---
Add connection messages for streaming replication. log_connections
was broken for a replication connection and no messages were
displayed on either standby or primary, at any debug level.
Connection messages needed to diagnose session drop/reconnect
events. Use LOG mode for
Log Message:
---
Minor tweaks on libpqrcv_connect(): ensure conninfo_repl[] is
correctly sized and expand comment to explain otherwise
undocumented use of replication connection parameter.
Modified Files:
--
pgsql/src/backend/replication/libpqwalreceiver:
libpqwalre
Log Message:
---
Update XLOG_PAGE_MAGIC to recognise WAL format changes.
Modified Files:
--
pgsql/src/include/access:
xlog_internal.h (r1.29 -> r1.30)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/xlog_internal.h?r1=1.29&r2=1.30)
--
S
Peter Eisentraut wrote:
Log Message:
---
Prevent the injection of invalidly encoded strings by PL/Python into PostgreSQL
with a few strategically placed pg_verifymbstr calls.
Awesome. Do we need to fix pltcl too?
cheers
andrew
--
Sent via pgsql-committers mailing list (pgsql-c
Log Message:
---
Adjust comment in .history file to match recovery target specified. Comment
present since 8.0 was never fully meaningful, since two recovery targets
cannot be specified. Refactor recovery target type to make this change
and associated code easier to understand. No change in
Log Message:
---
Reset btpo.xact following recovery of btree delete page. Add btpo_xact
field into WAL record and reset it from there, rather than using
FrozenTransactionId which can lead to some corner case bugs.
Problem report and suggested route to a fix from Heikki, details by me.
Mod
20 matches
Mail list logo
