Re: Errors when restoring backup created by pg_dumpall

On Thursday, December 5, 2024, Ron Johnson wrote: > On Thu, Dec 5, 2024 at 6:24 PM David G. Johnston < > david.g.johns...@gmail.com> wrote: > >> On Thu, Dec 5, 2024 at 4:04 PM Ron Johnson >> wrote: >> >>> Another alternative is to open the .sql file in Notepad++, then add >>> "public." before al

Re: Errors when restoring backup created by pg_dumpall

On 12/5/24 18:44, Ron Johnson wrote: On Thu, Dec 5, 2024 at 6:24 PM David G. Johnston mailto:david.g.johns...@gmail.com>> wrote: On Thu, Dec 5, 2024 at 4:04 PM Ron Johnson mailto:ronljohnso...@gmail.com>> wrote: Another alternative is to open the .sql file in Notepad++, then

Re: Errors when restoring backup created by pg_dumpall

On Thu, Dec 5, 2024 at 6:24 PM David G. Johnston wrote: > On Thu, Dec 5, 2024 at 4:04 PM Ron Johnson > wrote: > >> Another alternative is to open the .sql file in Notepad++, then add >> "public." before all the unqualified "earth" and "ll_to_earth" references. >> > > And as discussed there are n

Re: Best Practices for Managing Schema Changes Dynamically with libpq

On 2024-12-03 18:43 +0100, Sasmit Utkarsh wrote: > I am working on a project that uses libpq along with C language to interact > with PostgreSQL, and we face challenges with managing schema changes > dynamically in production while avoiding downtime. Specifically, we need > guidance on handling tab

Re: Errors when restoring backup created by pg_dumpall

On Thu, Dec 5, 2024 at 4:04 PM Ron Johnson wrote: > Another alternative is to open the .sql file in Notepad++, then add > "public." before all the unqualified "earth" and "ll_to_earth" references. > And as discussed there are none in that file because those references are within an extension's o

Re: Errors when restoring backup created by pg_dumpall

On Thu, Dec 5, 2024 at 5:32 PM PopeRigby wrote: > On 12/1/24 13:55, Tom Lane wrote: > > Adrian Klaver writes: > >> On 12/1/24 13:14, Tom Lane wrote: > >>> It would be useful to know what is the command at line 4102 > >>> of all.sql. > >> It is here: > >> https://gist.github.com/poperigby/fcb59eb

Re: Errors when restoring backup created by pg_dumpall

On 12/5/24 14:32, PopeRigby wrote: On 12/1/24 13:55, Tom Lane wrote: Adrian Klaver writes: On 12/1/24 13:14, Tom Lane wrote: It would be useful to know what is the command at line 4102 of all.sql. It is here: https://gist.github.com/poperigby/fcb59eb6c22c6051800e06a0ec482b49 CREATE TABLE pub

Re: Errors when restoring backup created by pg_dumpall

On 12/1/24 13:55, Tom Lane wrote: Adrian Klaver writes: On 12/1/24 13:14, Tom Lane wrote: It would be useful to know what is the command at line 4102 of all.sql. It is here: https://gist.github.com/poperigby/fcb59eb6c22c6051800e06a0ec482b49 CREATE TABLE public.geodata_places ( id intege

Re: Updated Fedora 40 and Fedora 41 RPM packages of Pgpool-II 4.5.5 in the repo

Hello, I'm talking about PGDG maintained repository (and not Fedora maintained) where pgpool is located: https://download.postgresql.org/pub/repos/yum/common/fedora/fedora-40-x86_64/ https://download.postgresql.org/pub/repos/yum/common/fedora/fedora-41-x86_64/ Currently installed package: pgpo

Re: Clarification of behaviour when dropping partitions

Yes, this is what I have done. But the whole point of declaring the foreign key constraint on the partitioned table is to have it automatically created on subsequent/future partitions. On Wed, Dec 4, 2024 at 6:20 PM Laurenz Albe wrote: > On Wed, 2024-12-04 at 14:22 +0100, Bolaji Wahab wrote: > >