Re: Recommended books for admin
Hi , Here is a lately published book https://www.amazon.com/PostgreSQL-Administration-Cookbook-real-world-challenges-ebook/dp/B0CP5PPSTQ Muhammad Ikram Bitnine Global On Tue, 25 Jun 2024 at 19:09, Bill Smith wrote: > Check out the left side bar > > Documentation <https://www.postgresql.org/docs/> > postgresql.org <https://www.postgresql.org/docs/> > [image: favicon.ico] <https://www.postgresql.org/docs/> > <https://www.postgresql.org/docs/> > > > On Jun 25, 2024, at 10:04 AM, Tom Browder wrote: > > I’m a complete novice, although I’ve dipped my toes in Admin waters a > couple of times in my many years of using Linux. > > Can anyone recommend a good book on installing Postgres on multiple, > connected multiuser systems, tuning it, managing users, backups, updated, > etc. > > A cookbook/checklist approach would be great. I’ve bought several books > over the years but a more current one is desirable. > > Thanks for any help. > > Best regards, > > -Tom > > > favicon.ico Description: Binary data
Re: New standby_slot_names GUC in PG 17
Thanks Tom Lane. You are more insightful. Regards, Ikram On Sat, Jun 22, 2024 at 12:50 AM Tom Lane wrote: > Muhammad Ikram writes: > > A humble input, as on primary we have #primary_slot_name = '' then > should > > not it be okay to have standby_slot_names or standby_slot_name ? It seems > > consistent with the Guc on primary. > > Another suggestion is *standby_replication_slots*. > > IIUC, Bruce's complaint is that the name is too generic (which I agree > with). Given the stated functionality: > > >>>> Allow specification of physical standbys that must be synchronized > >>>> before they are visible to subscribers (Hou Zhijie, Shveta Malik) > > it seems like the name ought to have some connection to > synchronization. Perhaps something like "synchronized_standby_slots"? > > I haven't read the patch, so I don't know if this name is especially > on-point. But "standby_slot_names" seems completely unhelpful, as > a server could well have slots that are for standbys but are not to > be included in this list. > > regards, tom lane > -- Muhammad Ikram
Re: New standby_slot_names GUC in PG 17
Hi, A humble input, as on primary we have #primary_slot_name = '' then should not it be okay to have standby_slot_names or standby_slot_name ? It seems consistent with the Guc on primary. Another suggestion is *standby_replication_slots*. Regards, Muhammad Ikram Bitnine Global. On Fri, Jun 21, 2024 at 8:47 PM Nathan Bossart wrote: > On Fri, Jun 21, 2024 at 11:37:54AM -0400, Bruce Momjian wrote: > > The release notes have this item: > > > > Allow specification of physical standbys that must be synchronized > > before they are visible to subscribers (Hou Zhijie, Shveta Malik) > > > > The new server variable is standby_slot_names. > > > > Is standby_slot_names an accurate name for this GUC? It seems too > > generic. > > +1, I was considering bringing this up, too. I'm still thinking of > alternate names to propose, though. > > -- > nathan > > > -- Muhammad Ikram
Re: Backup and Restore of Partitioned Table in PG-15
Hi Gayatri Singh, Could you try pgBackRest ? Its advantages are speed, support for incremental backups, minimal locking, and robust point in time recovery options besides several advanced features. Best suites for large-scale and critical PostgreSQL deployments. Regards, Muhammad Ikram Bitnine Global On Sun, Jun 16, 2024 at 4:09 AM Gayatri Singh wrote: > Hi Team, > > Greetings of the day!! > > We are planning to partition tables using pg_partman. Like we are planning > for their backup and restoration process. > > Got a few URLs where pg_dump had issues while restoring some data that was > lost. > > kindly guide me the process or steps I need to follow for backing up > partitioned tables correctly so that while restoration I don't face any > issue. > > Another question, currently we are using pg_dump for database backup which > locks tables and completely puts db transactions on hold. For this I want > tables shouldnt get locked also the backup process should complete in less > time. > > Thanks in advance!! > > Thanks & Regards, > Gayatri > > > -- Muhammad Ikram
Re: First draft of PG 17 release notes
Hi Bruce, A minor formatting issue in the start below. Bullet is not required here. E.1.1. Overview <https://momjian.us/pgsql_docs/release-17.html#RELEASE-17-HIGHLIGHTS> PostgreSQL 17 contains many new features and enhancements, including: - The above items and other new features of PostgreSQL 17 are explained in more detail in the sections below. Regards, Ikram On Thu, May 9, 2024 at 9:45 AM David Rowley wrote: > On Thu, 9 May 2024 at 16:04, Bruce Momjian wrote: > > I welcome feedback. For some reason it was an easier job than usual. > > Thanks for working on that. > > > +2023-11-02 [cac169d68] Increase DEFAULT_FDW_TUPLE_COST from 0.01 to 0.2 > > > +Double the default foreign data wrapper tuple cost (David Rowley, Umair > Shahid) > > That's 20x rather than 2x. > > David > > > -- Muhammad Ikram
