| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Robert Treat <rob(at)xzilla(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: small windows psqlrc re-wording |
| Date: | 2022-09-09 17:52:49 |
| Message-ID: | 168204.1662745969@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> On testing that in HEAD, I read
> Both the system-wide startup file and the user's personal startup file
> can be made psql-version-specific by appending a dash and the
> PostgreSQL major or minor release number to the file name, for example
> ~/.psqlrc-16 or ~/.psqlrc-16devel.
> That's a little confusing but it's actually accurate, because what
> process_psqlrc_file appends is the string PG_VERSION, so in a devel
> branch or beta release there's a non-numeric "minor release".
> I'm inclined to go ahead and do it like that.
I decided that what I found jarring about that was the use of "release
number" with a non-numeric version, so I changed it to "release
identifier" and pushed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2022-09-09 17:58:13 | Re: cataloguing NOT NULL constraints |
| Previous Message | Jaime Casanova | 2022-09-09 17:51:45 | Re: START_REPLICATION SLOT causing a crash in an assert build |