| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Joel Jacobson <joel(at)compiler(dot)org> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: [PATCH] Implement motd for PostgreSQL |
| Date: | 2021-04-03 15:50:16 |
| Message-ID: | alpine.DEB.2.22.394.2104031741320.1277015@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Perhaps the configuration-file parser has been fixed since to support
> embedded newlines? If so, then maybe it would actually be an idea to
> support newlines by escaping them?
Dunno.
If such a feature gets considered, I'm not sure I'd like to actually edit
pg configuration file to change the message.
The actual source looks pretty straightforward. I'm wondering whether pg
style would suggest to write motd != NULL instead of just motd.
I'm wondering whether it should be possible to designate (1) a file the
content of which would be shown, or (2) a command, the output of which
would be shown [ok, there might be security implications on this one].
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhihong Yu | 2021-04-03 16:14:33 | Re: CLUSTER on partitioned index |
| Previous Message | aditya desai | 2021-04-03 15:44:33 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |