Re: Enquiry about TDE with PgSQL

2025-11-07 Thread Bruce Momjian
On Mon, Nov 3, 2025 at 09:23:33PM -0800, Adrian Klaver wrote: > On 11/3/25 18:05, Bruce Momjian wrote: > > On Mon, Nov 3, 2025 at 07:42:06PM +0100, Laurenz Albe wrote: > > > On Mon, 2025-11-03 at 11:56 -0500, Bruce Momjian wrote: > > > > The problem with the Percona extension is it seems like it

Re: Enquiry about long-running queries

2025-11-07 Thread Adrian Klaver
On 11/7/25 05:48, Ashish Mukherjee wrote: Hello, I have a query like this showing up on my production database - The query when run from psql prompt finishes in a jiffy, so query What client is the stuck query being run from? Regards, Ashish -- Adrian Klaver [email protected]

Re: Enquiry about long-running queries

2025-11-07 Thread Laurenz Albe
On Fri, 2025-11-07 at 19:18 +0530, Ashish Mukherjee wrote: > I have a query like this showing up on my production database -  > > s05=> SELECT pid, user, usename, application_name, client_addr, > client_hostname, client_port, datname, now() - query_start as "runtime", > state, wait_event_type, wa

Re: Enquiry about long-running queries

2025-11-07 Thread Ron Johnson
On Fri, Nov 7, 2025 at 8:49 AM Ashish Mukherjee wrote: > Hello, > > I have a query like this showing up on my production database - > > s05=> SELECT pid, user, usename, application_name, client_addr, > client_hostname, client_port, datname, now() - query_start as "runtime", > state, wait_event_ty

Enquiry about long-running queries

2025-11-07 Thread Ashish Mukherjee
Hello, I have a query like this showing up on my production database - s05=> SELECT pid, user, usename, application_name, client_addr, client_hostname, client_port, datname, now() - query_start as "runtime", state, wait_event_type, wait_event, substr(query, 0, 100) FROM pg_stat_activity WHERE

Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)

2025-11-07 Thread Bala M
*1) Show how you have set up the publishers and subscribers.* We have configured logical replication between PostgreSQL 11 (publisher) and PostgreSQL 16 (subscriber). Publisher: PostgreSQL 11 with wal_level=logical, max_replication_slots=20, and publication created for all tables (FOR ALL TABLES)

Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)

2025-11-07 Thread Bala M
Hi Adrian, Thank you for your response. Please find the requested details below: *PostgreSQL Version:* Source: PostgreSQL 11.15 Target: PostgreSQL 16.9 *Operating System:* Source: RHEL 7.9 Target: RHEL 9.6 *Network Distance:* Both servers are in the same data center, connected through a hi