Re: Slow performance

2024-07-26 Thread David Rowley
On Fri, 26 Jul 2024 at 19:55, Francisco Olarte wrote: > " -> Index Scan using > ""cl_student_semester_subject_IX3"" on cl_student_semester_subject p > (cost=0.55..8.57 rows=1 width=60) (actual time=0.033..55.702 > rows=41764 loops=1)" > "Index Cond: (((companycode

Unexpected Null Pointer For Static Shared Memory Segment

2024-07-26 Thread Aditya Gupta
Hello, I hope this message finds you well. I am currently working on a PostgreSQL extension and have encountered an issue where a static pointer becomes null between different AM routines. My problem is as follows: I am working with a few AM routines, specifically “ambuild” and “amrescan”. Dur

Re: Slow performance

2024-07-26 Thread Fatih Sazan
Hi Siva, pg_dump taken from client_db seems not to have transferred full data to client_test. When I examine the query plans, the rows scanned seem to be extremely different. For example, there is 1 row in cl_level table on client_test, while clined_db shows that around 300,000 records were scann

Re: Slow performance

2024-07-26 Thread Francisco Olarte
Hello: On Fri, 26 Jul 2024 at 07:31, sivapostg...@yahoo.com wrote: ... > Took backup (pg_dump) of first database (client_db) and restored the database > as second database (client_test). ... > The query when run against DB1 takes around 7 min 32 seconds. > The same query when run against DB2 tak

Re: pgBackRest for multiple production servers

2024-07-26 Thread Kashif Zeeshan
Hi On Mon, Jul 22, 2024 at 9:35 AM KK CHN wrote: > Hi list , > > I am exploring the PgBackRest tool for production deployment. ( My lab > setup with one Database server and another Reposerver deployed working > fine as in the official docs) > > Query: > > What may be the standard practice emp