Skip site navigation (1) Skip section navigation (2)

pgsql: Fix syslogger to not lose log coherency under high load.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix syslogger to not lose log coherency under high load.
Date: 2012-04-04 19:06:32
Message-ID: E1SFVXM-0001dB-7n@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Fix syslogger to not lose log coherency under high load.

The original coding of the syslogger had an arbitrary limit of 20 large
messages concurrently in progress, after which it would just punt and dump
message fragments to the output file separately.  Our ambitions are a bit
higher than that now, so allow the data structure to expand as necessary.

Reported and patched by Andrew Dunstan; some editing by Tom

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/60243e89a707bb141aa1b164c2d6fb59e3e22408

Modified Files
--------------
src/backend/postmaster/syslogger.c |  132 +++++++++++++++++++-----------------
1 files changed, 71 insertions(+), 61 deletions(-)

pgsql-committers by date

Next:From: Tom LaneDate: 2012-04-04 20:15:31
Subject: pgsql: Remove useless PGRES_COPY_BOTH "support" in psql.
Previous:From: Tom LaneDate: 2012-04-04 00:44:15
Subject: pgsql: Fix a couple of contrib/dblink bugs.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group