Re: small windows psqlrc re-wording

From: Robert Treat <rob(at)xzilla(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: small windows psqlrc re-wording
Date: 2022-09-10 13:07:29
Message-ID: CAJSLCQ1JeG_bjOftvhO+K-2JoKp__ejK+AybzXGMEu5hvST3OA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 9, 2022 at 1:52 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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.
>

Looks good. Thanks Tom / Julien.

Robert Treat
https://xzilla.net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-09-10 14:32:20 Re: pg_toast.pg_toast_relfilenode not exist due to vacuum full tablename
Previous Message Melih Mutlu 2022-09-10 12:55:30 Re: Summary function for pg_buffercache