| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "okano(dot)naoki(at)fujitsu(dot)com" <okano(dot)naoki(at)fujitsu(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CR is not removed with psql -f command on Windows. |
| Date: | 2021-05-27 13:56:05 |
| Message-ID: | 1710293.1622123765@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"okano(dot)naoki(at)fujitsu(dot)com" <okano(dot)naoki(at)fujitsu(dot)com> writes:
> When creating a function with the psql -f filename command, the prosrc in pg_proc catalog contains \r(CR).
Does that cause you any actual problems?
> But I expect \r to be deleted. Is this a bug?
I'm kind of inclined to ignore it, mainly because of the law of unintended
consequences: adding code to strip \r is likely to break some scenario
that's working fine for somebody else.
I see that psql opens -f files with PG_BINARY_R, but that seems to be
a very ancient decision so I'm hesitant to change it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-05-27 15:11:48 | Re: BUG #17036: generated column cann't modifyed auto when update |
| Previous Message | Tom Lane | 2021-05-27 13:45:57 | Re: BUG #17036: generated column cann't modifyed auto when update |