On Mon, Oct 30, 2023 at 6:57 AM Alexander Kukushkin wrote:
...
> As Michael already said, the following workflow works just fine (I did it
> dozens of times):
> 1. enable checksums on the standby node
> 2. start the standby and let it catch up with the primary
> 3. switchover to a standby node
>
On 11/1/23 20:05, Brad White wrote:
*From:* Ron
*Sent:* Thursday, November 2, 2023 3:01:47 AM
*To:* pgsql-general@lists.postgresql.org
*Subject:* Re: pg_dump/pg_restore --jobs practical limit?
On 11/1/23 15:42, Laur
From: Ron
Sent: Thursday, November 2, 2023 3:01:47 AM
To: pgsql-general@lists.postgresql.org
Subject: Re: pg_dump/pg_restore --jobs practical limit?
On 11/1/23 15:42, Laurenz Albe wrote:
On Wed, 2023-11-01 at 13:09 -0500, Ron wrote:
I will "soon" migrate som
On 11/1/23 15:42, Laurenz Albe wrote:
On Wed, 2023-11-01 at 13:09 -0500, Ron wrote:
I will "soon" migrate some 1+ TB database from Pg 9.6.24 on RHEL 6 VMs to Pg
14.latest on RHEL 8 VMs. The VMs have 10Gbps "NICs", SAN-based LUNs managed
by LVM, and are all on ESX blades. nproc count on some is
On Wed, 2023-11-01 at 13:09 -0500, Ron wrote:
> I will "soon" migrate some 1+ TB database from Pg 9.6.24 on RHEL 6 VMs to Pg
> 14.latest on RHEL 8 VMs. The VMs have 10Gbps "NICs", SAN-based LUNs managed
> by LVM, and are all on ESX blades. nproc count on some is 16 and on others
> is 32.
>
>
Hi,
please don't top-post.
## Atul Kumar (akumar14...@gmail.com):
> I have already enabled log_hostname, still *client_hostname is not showing
> up.*
It's always helpful to mention relevant non-default settings along
with the question. Was log_hostname really active at backup start
time? (Chec
Yes, I have already tried that as log_hostname was already enabled by me.
By the way, just to inform you that the log_hostname is used for logging
the hostname instead of ip addresses in error log files only, Please
correct me if I am wrong.
Could you help me in telling my query that Iasked in my
Did you reconnect your replica after enabling log_hostname? If not, then do
it and check again.
śr., 1 lis 2023, 19:03 użytkownik Atul Kumar
napisał:
> I have already enabled log_hostname, still *client_hostname is not
> showing up.*
>
> Do you think that just because I use ip instead of hostna
I will "soon" migrate some 1+ TB database from Pg 9.6.24 on RHEL 6 VMs to Pg
14.latest on RHEL 8 VMs. The VMs have 10Gbps "NICs", SAN-based LUNs managed
by LVM, and are all on ESX blades. nproc count on some is 16 and on others
is 32.
Does anyone have experience as to the point of diminis
I have already enabled log_hostname, still *client_hostname is not showing
up.*
Do you think that just because I use ip instead of hostname while using
pg_basebackup could be the reason for it ?
Regards,
Atul
On Wed, Nov 1, 2023 at 11:23 PM Christoph Moench-Tegeder
wrote:
> ## Atul Kumar (
## Atul Kumar (akumar14...@gmail.com):
> It was successfully configured but when I query pg_stat_replication I don't
> get the hostname in output:
I Recommend The Fine Manual:
https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-REPLICATION-VIEW
"... and only when log_
Hi,
I have postgres 12 running in centos7.
I recently have configured streaming replication from master to standby
using below command:
/usr/bin/pg_basebackup -h -p 5432 -U replication -D
/path/of/data/directory/ -Fp -R -Xs -P -c fast
It was successfully configured but when I query pg_stat_rep
Thank you all for the answers, they covered me well.
Is this worth a bug report? I can file one if the issue is not known.
No. It's just a missing optimisation. We know about it.
It's good I shot an email first then. FWIW my usual way in other projects
would be to check the bugtracker, and
13 matches
Mail list logo
