Search found 10 matches
- 21.02.2024, 12:25
- Forum: PostgreSQL
- Topic: connecting via unix socket to a non-standard port
- Replies: 12
- Views: 2133
Re: connecting via unix socket to a non-standard port
databases where we have file names as database names ... So - I think if we want to support connectiong to unix domain sockets in non-standard locations, we should simply add another parameter that will be checked if the host name is empty. yes, you are right, for such an ambiguous situation, it is...
- 21.02.2024, 09:25
- Forum: PostgreSQL
- Topic: connecting via unix socket to a non-standard port
- Replies: 12
- Views: 2133
Re: connecting via unix socket to a non-standard port
(delete this message)
- 20.02.2024, 14:40
- Forum: PostgreSQL
- Topic: connecting via unix socket to a non-standard port
- Replies: 12
- Views: 2133
Re: connecting via unix socket to a non-standard port
and another question, according to LIBPQ-CONNSTRING-URIS : The host part is interpreted as described for the parameter host. In particular, a Unix-domain socket connection is chosen if the host part is either empty or looks like an absolute path name, otherwise a TCP/IP connection is initiated. Note...
- 20.02.2024, 12:45
- Forum: PostgreSQL
- Topic: connecting via unix socket to a non-standard port
- Replies: 12
- Views: 2133
Re: connecting via unix socket to a non-standard port
marsupilami, thanks for making the changes :) about an empty password (the ability to set an empty password and set it in the connection string) - I think, it needs to be filtered, because, according to CREATE ROLE , If no password is specified, the password will be set to null and password authenti...
- 17.02.2024, 21:07
- Forum: PostgreSQL
- Topic: connecting via unix socket to a non-standard port
- Replies: 12
- Views: 2133
Re: connecting via unix socket to a non-standard port
about how correct it is to specify only the port without the host in the URL - I looked at 34.1.1.2. Connection URIs , it says: 34.1.1.2. Connection URIs The general form for a connection URI is: postgresql://[userspec@][hostspec][/dbname][?paramspec] where userspec is: user[:password] and hostspec ...
- 17.02.2024, 20:56
- Forum: PostgreSQL
- Topic: connecting via unix socket to a non-standard port
- Replies: 12
- Views: 2133
Re: connecting via unix socket to a non-standard port
By the way, add both user and password at the same time, in line 794 of the ZDbcPostgreSql.pas file: if user <> '' then begin AddParamToResult('user', User); AddParamToResult('password', Password); end; is also a little incorrect: user authentication can be done via kerberos (by the way, it wouldn’t...
- 17.02.2024, 20:46
- Forum: PostgreSQL
- Topic: connecting via unix socket to a non-standard port
- Replies: 12
- Views: 2133
Re: connecting via unix socket to a non-standard port
as I understand it, the problem is that the current sources are not designed to use a port number without specifying a host: if only a port without a host is specified, then an incorrect URL is generated, in which the port is simply not added (/src/dbc/ZDbcIntfs.pas, lines 5001-5006): if HostName <>...
- 17.02.2024, 19:12
- Forum: PostgreSQL
- Topic: connecting via unix socket to a non-standard port
- Replies: 12
- Views: 2133
Re: connecting via unix socket to a non-standard port
(delete this message)
- 18.01.2024, 17:43
- Forum: PostgreSQL
- Topic: connecting via unix socket to a non-standard port
- Replies: 12
- Views: 2133
connecting via unix socket to a non-standard port
(I use google translate for english, sorry :) ) how can I connect to a local postgresql server via a unix socket in zeoslib, but when the DBMS is on a non-standard port (for example, 5433) ? debian 10 (astralinux 1.7 "Smolensk" :roll: ), lazarus 3.0.0, zeoslib r8073, postgresql 11, all def...
- 22.07.2023, 04:30
- Forum: PostgreSQL
- Topic: process "RAISE INFO" via zeoslib
- Replies: 1
- Views: 519
process "RAISE INFO" via zeoslib
(I use google translate for english, sorry :) ) I want to "catch" RAISE INFO messages from a PostgreSQL 9.6 server (for example, get two RAISE with a level below EXCEPTION after ExecSQL for the query "DO $$ BEGIN RAISE NOTICE 'test1, notice'; RAISE WARNING 'test2, warning'; END $$;&qu...