Feature request for INITCAP() function

2023-11-30 Thread Jeff Gerbracht
It would be great if there was a way to set exceptions to the 'word' delimiter list used in the INITCAP() function.For example, I have hyphenated words like blue-green or possessives and contractions like don't and cat's tail These become Blue-Green, Don'T and Cat'S Tail. Being able to pass

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Adrian Klaver
On 11/30/23 20:43, Matthias Apitz wrote: El día jueves, noviembre 30, 2023 a las 02:10:25p. m. -0800, Adrian Klaver escribió: On 11/30/23 12:35, Adrian Klaver wrote: On 11/30/23 10:35, Adrian Klaver wrote: On 11/30/23 09:27, Loles wrote: cd /etc/postgresql/14/ sudo rm -r main_old/  

Re: libpq crashing on macOS during connection startup

2023-11-30 Thread Tom Lane
John DeSoi writes: > On Nov 30, 2023, at 2:07 PM, Tom Lane wrote: >> What troubles me about that stack trace is the references to Heimdal. >> We gave up supporting Heimdal (and v16 explicitly rejects building >> with it) because its support for Kerberos credentials was too >> incomplete and

Re: Feature request for INITCAP() function

2023-11-30 Thread Laurenz Albe
On Thu, 2023-11-30 at 21:08 -0500, Jeff Gerbracht wrote: > It would be great if there was a way to set exceptions to the 'word' > delimiter list used in > the INITCAP() function.    For example, I have hyphenated words like > blue-green or > possessives and contractions like don't and cat's tail

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Matthias Apitz
El día jueves, noviembre 30, 2023 a las 02:10:25p. m. -0800, Adrian Klaver escribió: > On 11/30/23 12:35, Adrian Klaver wrote: > > On 11/30/23 10:35, Adrian Klaver wrote: > > > On 11/30/23 09:27, Loles wrote: > > > > > > cd /etc/postgresql/14/ > > sudo rm -r main_old/ > >   or > > sudo cp -r

Re: libpq crashing on macOS during connection startup

2023-11-30 Thread John DeSoi
> On Nov 30, 2023, at 2:07 PM, Tom Lane wrote: > > What troubles me about that stack trace is the references to Heimdal. > We gave up supporting Heimdal (and v16 explicitly rejects building > with it) because its support for Kerberos credentials was too > incomplete and flaky. So I'm

Re: libpq crashing on macOS during connection startup

2023-11-30 Thread Joe Conway
On 11/30/23 09:45, John DeSoi wrote: I have a macOS web server using Postgres that has been very stable until a month or two ago. If I restart the web server the problem seems to go away for a while, but starts happening again within days. I thought it was a PHP issue as discussed in the link

Two started cluster on the same data directory and port

2023-11-30 Thread Loles
Hi! I have this situation on a server that is giving me problems. postgres@hostname:~$ pg_lsclusters Ver Cluster Port Status OwnerData directory Log file 14 main 5432 online postgres /var/lib/postgresql/14/main /var/log/postgresql/postgresql-14-main.log 14 main_old 5432

libpq crashing on macOS during connection startup

2023-11-30 Thread John DeSoi
I have a macOS web server using Postgres that has been very stable until a month or two ago. If I restart the web server the problem seems to go away for a while, but starts happening again within days. I thought it was a PHP issue as discussed in the link below, but I just noticed in the crash

replication strange behavior

2023-11-30 Thread Atul Kumar
Hi, I have postgres 12 running in centos 7. I have configured streaming replication between one master and one standby server. In the pg_hba.conf file of the master server, I have put the standby server's hostname instead of IP and due to which replication got broken and I started getting below

Re: replication strange behavior

2023-11-30 Thread Ron Johnson
On Thu, Nov 30, 2023 at 3:41 PM Atul Kumar wrote: > Hi, > > I have postgres 12 running in centos 7. > > I have configured streaming replication between one master and one standby > server. > > In the pg_hba.conf file of the master server, I have put the standby > server's hostname instead of IP

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Adrian Klaver
On 11/30/23 12:35, Adrian Klaver wrote: On 11/30/23 10:35, Adrian Klaver wrote: On 11/30/23 09:27, Loles wrote: cd /etc/postgresql/14/ sudo rm -r main_old/   or sudo cp -r main_old Arrgh. sudo mv -r main_old Memo to self don't eat lunch and copy/paste at same time. -- Adrian

Re: libpq crashing on macOS during connection startup

2023-11-30 Thread John DeSoi
> On Nov 30, 2023, at 8:59 AM, Joe Conway wrote: > > Did you recently get an OpenSSL upgrade to v3.2.0? This is a shot in the > dark, but perhaps related to the discussion here? > >

Re: libpq crashing on macOS during connection startup

2023-11-30 Thread John DeSoi
> On Nov 30, 2023, at 9:36 AM, Adrian Klaver wrote: > > What starts happening? Random web process crashes when connecting to PostgreSQL. > > Does the Postgres log show anything? No. > > Postgres version? > > How was Postgres installed? PostgreSQL 15.4 installed with Homebrew. John

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Adrian Klaver
On 11/30/23 08:37, Loles wrote: Every time I stop the main_old cluster with sudo pg_ctlcluster stop 14 main_old, both are stopped. And when I raise sudo pg_ctlcluster start 14 main, both are raised. I don't know how I got into this situation and I don't know how to resolve it. Is there

Re: Fixing or Mitigating this ERROR: invalid page in block 35217 of relation base/16421/3192429

2023-11-30 Thread Abdul Qoyyuum
Hi Stephen, On Wed, Nov 29, 2023 at 5:53 PM Stephen Frost wrote: > Greetings, > > * Abdul Qoyyuum (aqoyy...@cardaccess.com.bn) wrote: > > Knowing that it's a data corruption issue, the only way to fix this is to > > vacuum and reindex the database. What was suggested was the following: > > > >

Re: Fixing or Mitigating this ERROR: invalid page in block 35217 of relation base/16421/3192429

2023-11-30 Thread Abdul Qoyyuum
Hi Chris, On Wed, Nov 29, 2023 at 7:38 PM Chris Travers wrote: > > > On Wed, Nov 29, 2023 at 4:36 PM Abdul Qoyyuum > wrote: > >> Hi all, >> >> Knowing that it's a data corruption issue, the only way to fix this is to >> vacuum and reindex the database. What was suggested was the following: >>

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Loles
Yes, it exists but it is obsolete. The files and directories are all dated 2022. It was obsolete and no longer valid, it could be deleted. Only the main cluster is correct. El jue, 30 nov 2023 a las 17:43, Adrian Klaver () escribió: > On 11/30/23 08:37, Loles wrote: > > Every time I stop the

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Adrian Klaver
On 11/30/23 05:37, Loles wrote: Hi! I have this situation on a server that is giving me problems. postgres@hostname:~$ pg_lsclusters Ver Cluster  Port Status Owner    Data directory              Log file 14  main     5432 online postgres /var/lib/postgresql/14/main

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Adrian Klaver
On 11/30/23 07:23, Adrian Klaver wrote: On 11/30/23 05:37, Loles wrote: Hi! I have this situation on a server that is giving me problems. postgres@hostname:~$ pg_lsclusters Ver Cluster  Port Status Owner    Data directory              Log file 14  main     5432 online postgres

Re: libpq crashing on macOS during connection startup

2023-11-30 Thread Adrian Klaver
On 11/30/23 06:45, John DeSoi wrote: I have a macOS web server using Postgres that has been very stable until a month or two ago. If I restart the web server the problem seems to go away for a while, but starts happening again within days. I thought it was a PHP issue as discussed in the link

Re: libpq crashing on macOS during connection startup

2023-11-30 Thread Adrian Klaver
On 11/30/23 07:49, John DeSoi wrote: On Nov 30, 2023, at 9:36 AM, Adrian Klaver wrote: What starts happening? Random web process crashes when connecting to PostgreSQL. Does the Postgres log show anything? No. To be clear, at the times the Web processes crash there is are no traces

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Loles
Every time I stop the main_old cluster with sudo pg_ctlcluster stop 14 main_old, both are stopped. And when I raise sudo pg_ctlcluster start 14 main, both are raised. I don't know how I got into this situation and I don't know how to resolve it. El jue, 30 nov 2023 a las 17:34, Loles ()

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Adrian Klaver
On 11/30/23 08:34, Loles wrote: Please reply to list also. Ccing list. Indeed, that is the problem, they are two different clusters, pointing to the same data directory and reading from the same port. I can't change the port because it is the same postgresql.conf I don't know how to

Re: libpq crashing on macOS during connection startup

2023-11-30 Thread John DeSoi
> On Nov 30, 2023, at 10:21 AM, Adrian Klaver wrote: > > To be clear, at the times the Web processes crash there is are no traces in > the Postgres log of an issue on the Postgres side? > > Is there evidence in the Postgres logs of what the Web process was doing just > before it crashed?

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Adrian Klaver
On 11/30/23 08:46, Loles wrote: Yes, it exists but it is obsolete. The files and directories are all dated 2022. It was obsolete and no longer valid, it could be deleted. Only the main cluster is correct. First try: vi /etc/postgresql/14/main_old/start.conf and change auto to

Re: libpq crashing on macOS during connection startup

2023-11-30 Thread Tom Lane
John DeSoi writes: >> On Nov 30, 2023, at 8:59 AM, Joe Conway wrote: >> Did you recently get an OpenSSL upgrade to v3.2.0? This is a shot in the >> dark, but perhaps related to the discussion here? >>

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Loles
No, they are not symbolic links. I have thought about moving the main_old directory somewhere else and it doesn't change anything because the cluster main_old is linked to the main data directory. In fact, neither the log nor any main_old data file changes, they are all from 2020. It's a strange

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Adrian Klaver
On 11/30/23 10:35, Adrian Klaver wrote: On 11/30/23 09:27, Loles wrote: root@hostname:~# pg_lsclusters Ver Cluster  Port Status Owner    Data directory              Log file *14  main     5432 online* postgres /var/lib/postgresql/14/main /var/log/postgresql/postgresql-14-main.log *14  

Re: Fixing or Mitigating this ERROR: invalid page in block 35217 of relation base/16421/3192429

2023-11-30 Thread Stephen Frost
Greetings, On Thu, Nov 30, 2023 at 02:51 Abdul Qoyyuum wrote: > On Wed, Nov 29, 2023 at 5:53 PM Stephen Frost wrote: > >> * Abdul Qoyyuum (aqoyy...@cardaccess.com.bn) wrote: >> > Knowing that it's a data corruption issue, the only way to fix this is >> to >> > vacuum and reindex the database.

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Adrian Klaver
On 11/30/23 09:27, Loles wrote: root@hostname:~# pg_lsclusters Ver Cluster  Port Status Owner    Data directory              Log file *14  main     5432 online* postgres /var/lib/postgresql/14/main /var/log/postgresql/postgresql-14-main.log *14  main_old 5432 online *postgres

PAF with Pacemaker

2023-11-30 Thread Vijaykumar Patil
Hi Team , I have two postgres server one is primary and other one replica, I have setup replication and configured pacemaker and corosync. But still I'm facing issue while creating resource. It is showing invalid parameters. [root@scrbtrheldbaas001 heartbeat]# pcs status Cluster name:

Re: Two started cluster on the same data directory and port

2023-11-30 Thread Loles
root@hostname:~# su - postgres postgres@hostname:~$ *nano /etc/postgresql/14/main_old/start.conf* postgres@hostname:~$ exit cerrar sesión root@hostname:~# *pg_ctlcluster stop 14 main* *(change auto for disabled and exit with save)* root@hostname:~# ps -ef | grep postgres root26091512

Re: replication strange behavior

2023-11-30 Thread Atul Kumar
Hi, In the master pg_hba.conf file, standby server hostname name is not being read even with the domain name, but server ip is working fine. output of /etc/hosts is given below 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost