Log Message:
---
Increase room for DateStyle storage.
If value is larger than buffer, it stays empty and libpq will drop connection.
Modified Files:
--
pgbouncer/include:
varcache.h (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbo
Log Message:
---
Dont let logging change errno.
With badly configured logging and higher logging levels, the code can
see wrong errno from syscalls. So always retore original errno when logging.
Modified Files:
--
pgbouncer/src:
util.c (r1.33 -> r1.34)
(h
Simon Riggs wrote:
> Log Message:
> ---
> Tune GetSnapshotData() during Hot Standby by avoiding loop
> through normal backends. Makes code clearer also, since we
> avoid various Assert()s. Performance of snapshots taken
> during recovery no longer depends upon number of read-only
> backends
Log Message:
---
Add wrapper function libpqrcv_PQexec() in the walreceiver that uses async
libpq to send queries, making the waiting for responses interruptible on
platforms where PQexec() can't normally be interrupted by signals, such
as win32.
Fujii Masao and Magnus Hagander
Modified Fi
Log Message:
---
Fix uninitialized local variables. Not sure why gcc doesn't complain about
these --- maybe because they're effectively unused? MSVC does complain though,
per buildfarm.
Modified Files:
--
pgsql/src/backend/access/nbtree:
nbtxlog.c (r1.65 -> r1.66)
Log Message:
---
Check RecoveryInProgress() while holding ProcArrayLock during snapshots.
This prevents a rare, yet possible race condition at the exact moment
of transition from recovery to normal running.
Modified Files:
--
pgsql/src/backend/storage/ipc:
procarray
Log Message:
---
Add new message for explicit rejection by pg_hba.conf. Implicit
rejection retains same message as before.
Modified Files:
--
pgsql/src/backend/libpq:
auth.c (r1.198 -> r1.199)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libp
Log Message:
---
Update docs as to when WAL logging can be skipped.
In 8.4 and prior, WAL-logging could potentially be skipped whenever
archive_mode=off. With streaming replication, this is now true only
if max_wal_senders=0.
Fujii Masao, with light copyediting by me
Modified Files:
---
On Mon, Apr 19, 2010 at 8:26 PM, Robert Haas wrote:
> Log Message:
> ---
> Update docs as to when WAL logging can be skipped.
>
> In 8.4 and prior, WAL-logging could potentially be skipped whenever
> archive_mode=off. With streaming replication, this is now true only
> if max_wal_senders=
Log Message:
---
Move the responsibility for calling StartupXLOG into InitPostgres, for
those process types that go through InitPostgres; in particular, bootstrap
and standalone-backend cases. This ensures that we have set up a PGPROC
and done some other basic initialization steps (corresp
10 matches
Mail list logo
