Clarification needed
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.
Cities name column name inconsistent
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/tutorial-fk.html Description: In earlier sections of the tutorial, the cities table had a column called 'name'. In this chapter, when creating the revised schema with foreign keys, the same column in the cities is now called 'city'.
TIMEZONE names
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/datatype-datetime.html Description: The documentation states that some timezone names are recognized. As far as I understand others aren't. This seems to be true: $psql postgres -c "set TIMEZONE='bug' ; show timezone;" ERROR: invalid value for parameter "TimeZone": "bug" $ echo $? 1 However adding a correct numerical offset leads Postgresql to accept a non-existing timezone name: $ psql postgres -c "set TIMEZONE='bug-1' ; show timezone;" $ echo $? 0 Thank you.
Re: TIMEZONE names
PG Doc comments form writes: > The documentation states that some timezone names are recognized. As far as > I understand others aren't. There is more detail about that at https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-TIMEZONES Note in particular that time zone abbreviations are not considered valid values for the TimeZone setting. However, once you add a numeric offset, the string becomes a valid POSIX-style setting. regards, tom lane
Re: Clarification needed
PG Doc comments form 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
Re: Cities name column name inconsistent
On Sat, Jun 12, 2021, 12:28 PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/tutorial-fk.html > Description: > > In earlier sections of the tutorial, the cities table had a column called > 'name'. In this chapter, when creating the revised schema with foreign > keys, > the same column in the cities is now called 'city'. > You are correct. I don't see an urgent need to spend time figuring out something different. David J.
Re: TIMEZONE names
On Sat, Jun 12, 2021, 12:28 PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/datatype-datetime.html > Description: > > The documentation states that some timezone names are recognized. As far > as > I understand others aren't. > > This seems to be true: > $psql postgres -c "set TIMEZONE='bug' ; show timezone;" > ERROR: invalid value for parameter "TimeZone": "bug" > $ echo $? > 1 > > However adding a correct numerical offset leads Postgresql to accept a > non-existing timezone name: > $ psql postgres -c "set TIMEZONE='bug-1' ; show timezone;" > $ echo $? > 0 > That would be the Appendix B material the documentation is referencing. David J. >
Re: Clarification needed
On 2021-06-12 12:47, Tom Lane wrote: PG Doc comments form 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.
