Log Message:
---
Remove docs for "Incrementally Updated Backups" because it was of
questionable reliability; information moved to a wiki:
http://wiki.postgresql.org/wiki/Incrementally_Updated_Backups
Backpatch to 9.0.
Tags:
REL9_0_STABLE
Modified Files:
--
Log Message:
---
Remove docs for "Incrementally Updated Backups" because it was of
questionable reliability; information moved to a wiki:
http://wiki.postgresql.org/wiki/Incrementally_Updated_Backups
Backpatch to 9.0.
Modified Files:
--
pgsql/doc/src/sgml:
Log Message:
---
Document filtering dictionaries in textsearch.sgml.
While at it, copy-edit the description of prefix-match marker support in
synonym dictionaries, and clarify the description of the default unaccent
dictionary a bit more.
Modified Files:
--
pgsql/doc/src/s
Log Message:
---
Document filtering dictionaries in textsearch.sgml.
While at it, copy-edit the description of prefix-match marker support in
synonym dictionaries, and clarify the description of the default unaccent
dictionary a bit more.
Tags:
REL9_0_STABLE
Modified Files:
Log Message:
---
Improve hint message for ENOMEM failure from shmget().
It turns out that some platforms return ENOMEM for a request that violates
SHMALL, whereas we were assuming that ENOSPC would always be used for that.
Apparently the latter is a Linuxism while ENOMEM is the BSD traditi
Log Message:
---
Improve hint message for ENOMEM failure from shmget().
It turns out that some platforms return ENOMEM for a request that violates
SHMALL, whereas we were assuming that ENOSPC would always be used for that.
Apparently the latter is a Linuxism while ENOMEM is the BSD traditi
Log Message:
---
Update release notes, per comments from Simon Riggs.
Tags:
REL9_0_STABLE
Modified Files:
--
pgsql/doc/src/sgml:
release-9.0.sgml (r2.39.2.10 -> r2.39.2.11)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release-9.0.sgml?
Log Message:
---
Update release notes, per comments from Simon Riggs.
Modified Files:
--
pgsql/doc/src/sgml:
release-9.0.sgml (r2.53 -> r2.54)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release-9.0.sgml?r1=2.53&r2=2.54)
--
Sent via pgsql
Log Message:
---
Catch null pointer returns from PyCObject_AsVoidPtr and PyCObject_FromVoidPtr
This is reproducibly possible in Python 2.7 if the user turned
PendingDeprecationWarning into an error, but it's theoretically also possible
in earlier versions in case of exceptional conditions
Log Message:
---
Catch null pointer returns from PyCObject_AsVoidPtr and PyCObject_FromVoidPtr
This is reproducibly possible in Python 2.7 if the user turned
PendingDeprecationWarning into an error, but it's theoretically also possible
in earlier versions in case of exceptional conditions
Log Message:
---
Catch null pointer returns from PyCObject_AsVoidPtr and PyCObject_FromVoidPtr
This is reproducibly possible in Python 2.7 if the user turned
PendingDeprecationWarning into an error, but it's theoretically also possible
in earlier versions in case of exceptional conditions
Log Message:
---
Catch null pointer returns from PyCObject_AsVoidPtr and PyCObject_FromVoidPtr
This is reproducibly possible in Python 2.7 if the user turned
PendingDeprecationWarning into an error, but it's theoretically also possible
in earlier versions in case of exceptional conditions
Log Message:
---
Catch null pointer returns from PyCObject_AsVoidPtr and PyCObject_FromVoidPtr
This is reproducibly possible in Python 2.7 if the user turned
PendingDeprecationWarning into an error, but it's theoretically also possible
in earlier versions in case of exceptional conditions
Log Message:
---
Catch null pointer returns from PyCObject_AsVoidPtr and PyCObject_FromVoidPtr
This is reproducibly possible in Python 2.7 if the user turned
PendingDeprecationWarning into an error, but it's theoretically also possible
in earlier versions in case of exceptional conditions
Log Message:
---
Catch null pointer returns from PyCObject_AsVoidPtr and PyCObject_FromVoidPtr
This is reproducibly possible in Python 2.7 if the user turned
PendingDeprecationWarning into an error, but it's theoretically also possible
in earlier versions in case of exceptional conditions
Robert Haas writes:
> On Wed, Aug 25, 2010 at 11:46 AM, Simon Riggs wrote:
>> I have a horrible nagging feeling this breaks something.
> Well, the only place it's used at the moment is in the drop-object
> code. Not sure if that might be enough to jog your memory?
Also, it's pretty hard to see
Log Message:
---
Add missing description of reloftype field
Tags:
REL9_0_STABLE
Modified Files:
--
pgsql/doc/src/sgml:
catalogs.sgml (r2.225.2.1 -> r2.225.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/catalogs.sgml?r1=2.225.2.1&r2=
Log Message:
---
Add missing description of reloftype field
Modified Files:
--
pgsql/doc/src/sgml:
catalogs.sgml (r2.226 -> r2.227)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/catalogs.sgml?r1=2.226&r2=2.227)
--
Sent via pgsql-committers
On Wed, Aug 25, 2010 at 11:46 AM, Simon Riggs wrote:
> On Mon, 2010-08-16 at 02:02 +, Robert Haas wrote:
>> Log Message:
>> ---
>> Make LockDatabaseObject() AcceptInvalidationMessages().
>>
>> This is appropriate for the same reasons we already do it in
>> LockSharedObject(): things mi
On Mon, 2010-08-16 at 02:02 +, Robert Haas wrote:
> Log Message:
> ---
> Make LockDatabaseObject() AcceptInvalidationMessages().
>
> This is appropriate for the same reasons we already do it in
> LockSharedObject(): things might have changed while we were waiting
> for the lock. There
On Thu, 2010-08-12 at 23:24 +, Robert Haas wrote:
> Log Message:
> ---
> Correct sundry errors in Hot Standby-related comments.
These look good, thanks.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-com
On Fri, 2010-08-13 at 15:42 +, Robert Haas wrote:
> Log Message:
> ---
> Make RecordTransactionCommit() respect wal_level.
>
> Since the only purpose of WAL-loggin SharedInvalidationMessages is to support
> Hot Standby operation, they needn't be included when wal_level < hot_standby.
>
Log Message:
---
Workaround for RelFileNodeBackend in 9.1.
Modified Files:
--
pgbulkload/lib:
pg_btree.c (r1.19 -> r1.20)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbulkload/pgbulkload/lib/pg_btree.c?r1=1.19&r2=1.20)
writer_direct.c (r1.10 -> r1
Log Message:
---
typos
Modified Files:
--
slony-ctl/outils:
01_create_init.sh (r1.12 -> r1.13)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/01_create_init.sh?r1=1.12&r2=1.13)
--
Sent via pgsql-committers mailing list (pgsql-com
24 matches
Mail list logo
