public inbox for [email protected]  

help / color / mirror / Atom feed

Clarification needed
3+ messages / 3 participants
[nested] [flat]

* Clarification needed
@ 2021-06-12 03:59  PG Doc comments form <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: PG Doc comments form @ 2021-06-12 03:59 UTC (permalink / raw)
  To: [email protected]; +Cc: [email protected]

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/13/libpq-pgpass.html
Description:

Web page https://www.postgresql.org/docs/13/libpq-pgpass.html

Are the fields in the .pgpass file case sensitive by default?  Obviously the
password is, & it appears that at least the username is.


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Clarification needed
@ 2021-06-12 19:47  Tom Lane <[email protected]>
  parent: PG Doc comments form <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2021-06-12 19:47 UTC (permalink / raw)
  To: [email protected]; +Cc: [email protected]

PG Doc comments form <[email protected]> writes:
> Are the fields in the .pgpass file case sensitive by default?

Yes.  User name and database name clearly must preserve case
distinctions.  Maybe there is an argument for the host name
to be matched case-insensitively, but I think it could cause
problems when the host string is a socket path name.

			regards, tom lane





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Clarification needed
@ 2021-06-13 01:23  Dean Gibson (DB Administrator) <[email protected]>
  parent: Tom Lane <[email protected]>
  0 siblings, 0 replies; 3+ messages in thread

From: Dean Gibson (DB Administrator) @ 2021-06-13 01:23 UTC (permalink / raw)
  To: Tom Lane <[email protected]>; +Cc: [email protected]

On 2021-06-12 12:47, Tom Lane wrote:
> PG Doc comments form <[email protected]> writes:
>> Are the fields in the .pgpass file case sensitive by default?
> Yes.  User name and database name clearly must preserve case
> distinctions.  Maybe there is an argument for the host name
> to be matched case-insensitively, but I think it could cause
> problems when the host string is a socket path name.
>
> 			regards, tom lane

No argument from me;  I like it the way it is.  I just posted the 
comment as a potential update to the web page.  Unless it is covered 
elsewhere.


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

end of thread, other threads:[~2021-06-13 01:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-06-12 03:59 Clarification needed PG Doc comments form <[email protected]>
2021-06-12 19:47 ` Tom Lane <[email protected]>
2021-06-13 01:23   ` Dean Gibson (DB Administrator) <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox