[COMMITTERS] textsearch-ja - textsearch_senna: Fix a bug that the second or later

2010-04-16 Thread User Itagaki
Log Message: --- Fix a bug that the second or later conditions had been ignored. Reported and fixed by Hitoshi Harada. The change also fixes other two bugs: - Memory leak when converting a LIKE query into a senna query. - Words that contain senna meta characters were treated wrongly.

[COMMITTERS] pgsql: In standby mode, suppress repeated LOG messages about a corrupt

2010-04-16 Thread Heikki Linnakangas
Log Message: --- In standby mode, suppress repeated LOG messages about a corrupt record, which just indicates that we've reached the end of valid WAL found in the standby. Modified Files: -- pgsql/src/backend/access/transam: xlog.c (r1.396 - r1.397)

[COMMITTERS] pgsql: On Windows, syslogger runs in two threads.

2010-04-16 Thread Heikki Linnakangas
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

[COMMITTERS] pgsql: On Windows, syslogger runs in two threads.

2010-04-16 Thread Heikki Linnakangas
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

[COMMITTERS] pgsql: On Windows, syslogger runs in two threads.

2010-04-16 Thread Heikki Linnakangas
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

[COMMITTERS] pgsql: On Windows, syslogger runs in two threads.

2010-04-16 Thread Heikki Linnakangas
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

[COMMITTERS] pgsql: Provide better guidance for adjusting shared_buffers.

2010-04-16 Thread Robert Haas
Log Message: --- Provide better guidance for adjusting shared_buffers. Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.266 - r1.267) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml?r1=1.266r2=1.267) -- Sent via

Re: [COMMITTERS] pgsql: Provide better guidance for adjusting shared_buffers.

2010-04-16 Thread David Fetter
On Fri, Apr 16, 2010 at 09:46:07PM +, Robert Haas wrote: Log Message: --- Provide better guidance for adjusting shared_buffers. Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.266 - r1.267)

Re: [COMMITTERS] pgsql: Provide better guidance for adjusting shared_buffers.

2010-04-16 Thread Robert Haas
On Fri, Apr 16, 2010 at 7:17 PM, David Fetter da...@fetter.org wrote: On Fri, Apr 16, 2010 at 09:46:07PM +, Robert Haas wrote: Log Message: --- Provide better guidance for adjusting shared_buffers. Modified Files: --     pgsql/doc/src/sgml:         config.sgml

Re: [COMMITTERS] pgsql: Provide better guidance for adjusting shared_buffers.

2010-04-16 Thread Jaime Casanova
On Fri, Apr 16, 2010 at 6:22 PM, Robert Haas robertmh...@gmail.com wrote: On Fri, Apr 16, 2010 at 7:17 PM, David Fetter da...@fetter.org wrote: On Fri, Apr 16, 2010 at 09:46:07PM +, Robert Haas wrote: Log Message: --- Provide better guidance for adjusting shared_buffers.