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
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/
or
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 m
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 in
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 flaky
> 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 inclined
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 localhost.localdom
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 Kla
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 a
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
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 main_old
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 ca
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?
>> https://www.postgresql.org/message-id/flat/CAN55FZ1eDDYsYaL7mv%2BoSLUij2h_u6hvD4Qmv-7PK7jkji0uy
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: pg_clust
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 /var/lib/postgresq
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. W
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 0
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 mai
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 disabled.
> 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?
N
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 both
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 disassoc
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 () escribió
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
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:
>>
>
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:
> >
> > S
> 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
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
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 /var/lib/postgre
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
/var/log/postgresql/postgres
> 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?
>
> https://www.postgresql.org/message-id/flat/CAN55FZ1eDDYsYaL7mv%2BoSLUij2h_u6hvD4Qmv-7PK7jkji0uyQ%40mail.gmail.c
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
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
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 on
34 matches
Mail list logo
