| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] log_line_info |
| Date: | 2004-03-09 16:01:11 |
| Message-ID: | 25641.1078848071@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>> After this is applied (fingers crossed) and everyone is happy, I will
>>> submit a patch to remove log_timestamp, log_pid and (if we are agreed on
>>> it) log_source_port.
> Is there agreement on removing these 3 config vars?
Now that I look at it, log_source_port does look pretty useless.
While you are at it, please clean up the confusion about whether
port->remote_host contains the port number or not (IMHO it should never
do so; BackendInit() is doing things in the wrong order).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2004-03-09 16:28:36 | Re: [HACKERS] Need packaging help for RPMs. |
| Previous Message | Lamar Owen | 2004-03-09 15:55:49 | Need packaging help for RPMs. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2004-03-09 16:38:17 | Re: [PATCHES] log_line_info |
| Previous Message | Tom Lane | 2004-03-09 15:41:09 | Re: [PATCHES] NO WAIT ... |