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-0001d8-5U@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
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
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/c17e863bc7677a54d6da5bbb2868cca2cd9b30c1

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

Browse pgsql-committers by date

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