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

Re: Various fixes for syslogger

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Various fixes for syslogger
Date: 2007-09-22 18:22:21
Message-ID: 1358.1190485341@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> writes:
> Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> Can you pinpoint where this change in argv/argc was made? I'm having 
>> trouble locating it.

> Oops, I misread the codes. There was the same bug in 8.0, too.
> Therefore, the fix should be appled to 8.0, 8.1, 8.2 and 8.3dev.
> We've had the bug in all versions after syslogger was added.

I've applied this fix, but only as far back as 8.2, on two grounds:
1. It's only likely to be of interest to developers.
2. We are no longer supporting 8.0 or 8.1 on Windows.

While it's theoretically not a Windows-specific bug, in practice
no one is going to use the EXEC_BACKEND option on other platforms.

			regards, tom lane

In response to

pgsql-patches by date

Next:From: Tom LaneDate: 2007-09-22 19:11:32
Subject: Re: [PATCHES] Patch to update log levels
Previous:From: Andrew DunstanDate: 2007-09-22 16:35:48
Subject: Re: ilike multi-byte pattern cache

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