Re: psql's default database on connect (our internal ref. SRP-30861)

Le ven. 6 août 2021 à 08:53, Matthias Apitz a écrit : > > Hello, > > testpos@srap53dxr1:~> psql --help > ... > -d, --dbname=DBNAME database name to connect to (default: "testpos") > > testpos@srap53dxr1:~> whoami > testpos > > testpos@srap53dxr1:~> env | grep PG > PGPASSWORD= > P

Re: psql's default database on connect (our internal ref. SRP-30861)

On Friday, August 6, 2021, Guillaume Lelarge wrote: > If unset, it will use the PostgreSQL user name also as the database name. > This is true, but its not what the docs says: psql usage doc: “The default user name is your operating-system user name, as is the default database name.” Specifyi

Re: psql's default database on connect (our internal ref. SRP-30861)

El día viernes, agosto 06, 2021 a las 09:07:56a. m. +0200, Guillaume Lelarge escribió: > Le ven. 6 août 2021 à 08:53, Matthias Apitz a écrit : > > > > > Hello, > > > > testpos@srap53dxr1:~> psql --help > > ... > > -d, --dbname=DBNAME database name to connect to (default: "testpos") > >

Re: psql's default database on connect (our internal ref. SRP-30861)

Le ven. 6 août 2021 à 09:25, Matthias Apitz a écrit : > El día viernes, agosto 06, 2021 a las 09:07:56a. m. +0200, Guillaume > Lelarge escribió: > > > Le ven. 6 août 2021 à 08:53, Matthias Apitz a écrit : > > > > > > > > Hello, > > > > > > testpos@srap53dxr1:~> psql --help > > > ... > > > -d

Re: psql's default database on connect (our internal ref. SRP-30861)

El día viernes, agosto 06, 2021 a las 09:34:42a. m. +0200, Guillaume Lelarge escribió: > > No, it does not match all my examples. Read again what it says as > > default on --help. > > > > Actually, it does. You launched "psql --help" without specifying a > PostgreSQL username and database name,

Re: psql's default database on connect (our internal ref. SRP-30861)

Le ven. 6 août 2021 à 09:51, Matthias Apitz a écrit : > El día viernes, agosto 06, 2021 a las 09:34:42a. m. +0200, Guillaume > Lelarge escribió: > > > > No, it does not match all my examples. Read again what it says as > > > default on --help. > > > > > > > Actually, it does. You launched "psql -

Re: psql's default database on connect (our internal ref. SRP-30861)

On Fri, Aug 06, 2021 at 08:53:22AM +0200, Matthias Apitz wrote: > What do I uderstand wrong? Please check https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-PARAMKEYWORDS Specifically: > dbname : The database name. Defaults to be the same as the user name. > In certain con

Re: psql's default database on connect (our internal ref. SRP-30861)

Matthias Apitz writes: > Sorry, it does not: > testpos@srap53dxr1:~> psql --help -Usisis | grep DBNAME > psql [OPTION]... [DBNAME [USERNAME]] > -d, --dbname=DBNAME database name to connect to (default: "testpos") While that's certainly confusing, I'm not sure it's wrong. I'd interpret "

TLS 1.0

Hi Team, Our client is using Version : PostgreSQL 9.6.17 , they have done vulnerability assessment and found that : - TLS version 1.0 Protocol detection - The remote service encrypt traffic with older version of TLS We suggested the below changes in PostgresSQL.conf ssl_ciphers = 'HIGH:

Re: sort order

On 27.07.21 19:07, Marc Millas wrote: so, obviously, both lc_collate knows about the é but obviously, too, they do behave differently on the impact of the beginning white space. I didn't see anything about this behaviour on the doc, unless the reference at the libc should be understood as ple

Re: TLS 1.0

Ehtesham Pradhan writes: > Our client is using Version : PostgreSQL 9.6.17 , they have done > vulnerability > assessment and found that : >- TLS version 1.0 Protocol detection >- The remote service encrypt traffic with older version of TLS This is mostly a matter of whether the OpenSSL

Re: TLS 1.0

>From a security audit point of view, also consider the fact that 9.6 is end-of-life in 3 months. -Steve On Fri, Aug 6, 2021 at 9:46 AM Tom Lane wrote: > Ehtesham Pradhan writes: > > Our client is using Version : PostgreSQL 9.6.17 , they have done > vulnerability > > assessment and found that

Re: PostgreSQL reference coffee mug

I suggest a series: one per chapter! > On Aug 6, 2021, at 12:09 PM, Matthias Apitz wrote: > > > The prototype is ready. > > matthias > > -- > Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub > Tear it down!

Re: pgcrypto - real life examples to encrypt / decrypt

someone mentioned an alternative earlier that they couldn't remember -- i think it may have been pgsodium that they were thinking of https://github.com/michelp/pgsodium

question about sql comments in postgresql server logs

Hello all, In order to track down some bugs, we thought it would be useful to append some comments to the sql being sent to postgresql like this:     select foo from bar   -- a comment with some metadata however, the postgresql server was not including the appended comment in the log file. If we

Re: question about sql comments in postgresql server logs

On 06/08/2021 20:08, Alan Stange wrote: > Hello all, > > In order to track down some bugs, we thought it would be useful to > append some comments to the sql being sent to postgresql like this: > select foo from bar -- a comment with some metadata > however, the postgresql server was not inc

Re: question about sql comments in postgresql server logs

Alan Stange writes: > In order to track down some bugs, we thought it would be useful to > append some comments to the sql being sent to postgresql like this: >     select foo from bar   -- a comment with some metadata > however, the postgresql server was not including the appended comment in > th

Re: question about sql comments in postgresql server logs

On 8/6/21 3:14 PM, Tom Lane wrote: > Alan Stange writes: >> In order to track down some bugs, we thought it would be useful to >> append some comments to the sql being sent to postgresql like this: >>     select foo from bar   -- a comment with some metadata >> however, the postgresql server was n

Re: pgcrypto - real life examples to encrypt / decrypt

How do those of us who compile PostgreSQL from source get libsodium into the mix? On Fri, Aug 6, 2021 at 2:27 PM Reid Thompson wrote: > someone mentioned an alternative earlier that they couldn't remember -- i > think it may have been pgsodium that they were thinking of > https://github.com/mich

Re: pgcrypto - real life examples to encrypt / decrypt

On 8/6/21 12:23 PM, Theodore M Rolle, Jr. wrote: How do those of us who compile PostgreSQL from source get libsodium into the mix? Have your package manager install it. OR https://doc.libsodium.org/ On Fri, Aug 6, 2021 at 2:27 PM Reid Thompson > wrote:

Re: PostgreSQL reference coffee mug

On 8/6/21 11:09 AM, Matthias Apitz wrote: The prototype is ready. +1 matthias -- Adrian Klaver adrian.kla...@aklaver.com

Re: Series of 10 questions about the use of postgresql, generally.

On 6/08/21 4:45 pm, A Z wrote: I have been going through the free online book LEARNING postgresql book, that has been compiled by Stack Overflow contributors. I have gotten to the point where I have the following series of unanswered questions: [...] 9. What does the VARYING keyword do to a

Re: Series of 10 questions about the use of postgresql, generally.

On 8/6/21 1:11 AM, Pavel Stehule wrote: 2. If I am using the COPY command for input and output around *.csv files, how may I specify internal tuple delimiters of ',', but at the same time also specify an end of line delimeter of ';' ? you cannot to specify end of l