| From: | heikki(at)postgresql(dot)org (Heikki Linnakangas) | 
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org | 
| Subject: | pgsql: On Windows, syslogger runs in two threads. | 
| Date: | 2010-04-16 09:52:15 | 
| Message-ID: | 20100416095215.84BCA7541D1@cvs.postgresql.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-committers | 
Log Message:
-----------
On Windows, syslogger runs in two threads. The main thread processes config
reload and rotation signals, and a helper thread reads messages from the
pipe and writes them to the log file. However, server code isn't generally
thread-safe, so if both try to do e.g palloc()/pfree() at the same time,
bad things will happen. To fix that, use a critical section (which is like
a mutex) to enforce that only one the threads are active at a time.
Tags:
----
REL8_2_STABLE
Modified Files:
--------------
    pgsql/src/backend/postmaster:
        syslogger.c (r1.29.2.5 -> r1.29.2.6)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/syslogger.c?r1=1.29.2.5&r2=1.29.2.6)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-04-16 21:46:07 | pgsql: Provide better guidance for adjusting shared_buffers. | 
| Previous Message | Heikki Linnakangas | 2010-04-16 09:52:01 | pgsql: On Windows, syslogger runs in two threads. |