Re: PORT 5432 ERROR

On 01.08.23 01:18, David Beck wrote: I am receiving an error when I enter the server port number to listen to—installed on all available versions, both 32-bit and 64-bit when applicable, even the latest version, 15.3 x64 for Windows. I downloaded the latest version as an example, and as I was

Re: error: connection to server on socket...

On 01.08.23 12:22, Amn Ojee Uw wrote: Using the following command on my Debian 12 machine: sudo apt-get install postgresql postgresql-15 postgresql-client-common postgresql-common postgresql-contrib postgresql-doc phppgadmin and following the instruction on this

Re: Regarding SSL Enablement in PostgreSQL Database on different port

On 02.05.23 12:13, Magnus Hagander wrote: On Tue, May 2, 2023 at 11:43 AM sujay kadam wrote: Hi PostgreSQL Team, I want to enable SSL in PostgreSQL Database on a new port. I don’t want the default port that is 5432 SSL enabled, but I want to configure another port to enable SSL on it. As

Re: Properly handle OOM death?

On 13.03.23 21:25, Joe Conway wrote: Hmm, well big +1 for having swap turned on, but I recommend setting "vm.overcommit_memory=2" even so. I've snipped out the context here, since my advice is very unspecific: do use swap only as a safety net. Once your system starts swapping performance

Re: Getting error while upgrading postgres from version 12 to 13

On Sun, Mar 19, 2023 at 2:09 AM shashidhar Reddy mailto:shashidharreddy...@gmail.com>> wrote: Hello, I am in a process of upgrading postgresql from version 12 to 13 using pg_upgrdrade but I am getting error stating  FATAL:  database files are incompatible with server  

Re: Getting error while upgrading postgres from version 12 to 13

On 18.03.23 22:24, shashidhar Reddy wrote: and adding to this the following is also showing in the error, we tried changing the file permissions but still no luck FATAL:  could not load private key file "/etc/ssl/private/ssl-cert-snakeoil.key": key values mismatch This sounds like the private

Re: can't get psql authentication against Active Directory working

Hi Stephen, On 25.02.23 00:52, Stephen Frost wrote: * Tomas Pospisek (t...@sourcepole.ch) wrote: >> On 21.02.23 16:29, Stephen Frost wrote: * Tomas Pospisek (t...@sourcepole.ch) wrote: On 20.02.23 15:17, Stephen Frost wrote: * Tomas Pospisek (t...@sourcepole.ch) wrote: >>

Re: can't get psql authentication against Active Directory working

Hi Stephen, again thanks a lot for trying to help me! On 21.02.23 16:29, Stephen Frost wrote: * Tomas Pospisek (t...@sourcepole.ch) wrote: On 20.02.23 15:17, Stephen Frost wrote: * Tomas Pospisek (t...@sourcepole.ch) wrote: so I'm trying to authenticate psql (on Windows) -> postg

Re: can't get psql authentication against Active Directory working

Hi Stephen, first: thanks a lot for replying! On 20.02.23 15:17, Stephen Frost wrote: * Tomas Pospisek (t...@sourcepole.ch) wrote: so I'm trying to authenticate psql (on Windows) -> postgres (on Linux) via Active Directory. Looks like you're trying to do a bit more than that as you

Re: can't get psql authentication against Active Directory working

On 18.02.23 17:16, Erik Wienhold wrote: On 18/02/2023 15:02 CET Tomas Pospisek wrote: so I'm trying to authenticate psql (on Windows) -> postgres (on Linux) via Active Directory. psql (Linux) -> postgres (Linux) with authentication against Active Directory does work. However th

can't get psql authentication against Active Directory working

Hello all, so I'm trying to authenticate psql (on Windows) -> postgres (on Linux) via Active Directory. psql (Linux) -> postgres (Linux) with authentication against Active Directory does work. However the same with psql.exe on Windows does not. I get: D:\>C:\OSGeo4W\bin\psql.exe

Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)

On 23.06.22 20:21, Adrian Klaver wrote: On 6/23/22 10:11, Adrian Klaver wrote: On 6/23/22 00:37, Tomas Pospisek wrote: On 22.06.22 22:18, Tomas Pospisek wrote: On 22.06.22 21:25, Adrian Klaver wrote: On 6/22/22 12:17, Tomas Pospisek wrote: So I used both pg_dump and pg_restore from

Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)

On 22.06.22 22:18, Tomas Pospisek wrote: On 22.06.22 21:25, Adrian Klaver wrote: On 6/22/22 12:17, Tomas Pospisek wrote: Hi all, while doing `cat pg_dump.dump | psql` I get the above message. Note that `pg_dump.dump` contains: CREATE DATABASE some_db WITH TEMPLATE = my_own_template

Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)

On 22.06.22 21:25, Adrian Klaver wrote: On 6/22/22 12:17, Tomas Pospisek wrote: Hi all, while doing `cat pg_dump.dump | psql` I get the above message. Note that `pg_dump.dump` contains: CREATE DATABASE some_db WITH TEMPLATE = my_own_template ENCODING = 'UTF8' LC_COLLATE = 'en_US.UTF-8

ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)

Hi all, while doing `cat pg_dump.dump | psql` I get the above message. Note that `pg_dump.dump` contains: CREATE DATABASE some_db WITH TEMPLATE = my_own_template ENCODING = 'UTF8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8'; What is exactly the problem? I understand that

Re: Reg: User creation script/List of privileges

On 30.03.22 05:09, Sai Ch wrote: Hi Experts, I am looking for a query or possibility to generate all the privileges a user/role has. I need this to create a user/role from one database to another with exact same privileges. Kindly, share the query or way to proceed further. Thanks &

Re: Detecting schema changes via WAL logs

On 19.02.22 17:42, Cal Mitchell wrote: Hello everyone, I’m building an open-source data integration tool (SQLpipe) and am now trying to incorporate CDC into the product. Is it possible to detect when schema changes happen via the WAL? The WAL doesn’t have to tell me /what/ was changed, it

Re: Strange results when casting string to double

On 18.02.22 22:42, Peter J. Holzer wrote: If there has been a glibc update (or a postgresql update) in those 480 days (Ubuntu 14.04 is out of its normal maintenance period but ESM is still available) the running processes may well run different code than a newly started program. So it could be

Fwd: PgAdmin is struggling and can we configure it so that it works better

Forgot to include pgsql-general@lists.postgresql.org in the Cc... Forwarded Message Subject: Re: PgAdmin is struggling and can we configure it so that it works better Date: Fri, 21 Jan 2022 13:42:13 +0100 From: Tomas Pospisek To: Shaozhong SHI On 21.01.22 12:42, Shaozhong

Re: postgresql11: How to use publication/subscription on primary/standby setup

On 29.09.21 11:01, Abhishek B wrote: Is there a solution to use publication/subscription on a master-slave or primary-standby postgres setup without manual intervention? Currently the DB clusters are managed by Pacemaker. Once there is a failover, the pacemaker is able to promote the

Re: Fastest option to transfer db?

I'm potentiall facing the same problem and would be interested in the solution. Is there any particular howto you followed? Also at some point I'd like to cut of the link between the two DBs promote the copy to be the master and delete the original DB. Have you figured out the correct step

Re: WAL accumulating, Logical Replication pg 13

Hi Willy-Bas Loos, On 31.05.21 17:32, Willy-Bas Loos wrote: On Mon, May 31, 2021 at 4:24 PM Vijaykumar Jain > wrote: So I got it all wrong it seems :) Thank you for taking the time to help me! You upgraded to pg13 fine? , but while on pg13

Re: very long secondary->primary switch time

Hi Tom, hi list participants, thanks a lot for replying Tom. On 27.04.21 22:16, Tom Lane wrote: Tomas Pospisek writes: I maintain a postgresql cluster that does failover via patroni. The problem is that after a failover happens it takes the secondary too long (that is about 35min) to come up

very long secondary->primary switch time

Hello all, I maintain a postgresql cluster that does failover via patroni. The problem is that after a failover happens it takes the secondary too long (that is about 35min) to come up and answer queries. The log of the secondary looks like this: 04:00:29.777 [9679] LOG: received promote