Re: unable to install postgreql 13.4

Hi, On Thu, Nov 03, 2022 at 12:18:05PM +0530, shashidhar Reddy wrote: > > I need to install postgresql 13.4 on development server , but getting below > errors, please help to resolve this > > sudo apt-get install postgresql-13.4 > > Reading package lists... Done > Building dependency tree > Readin

unable to install postgreql 13.4

Hello, I need to install postgresql 13.4 on development server , but getting below errors, please help to resolve this sudo apt-get install postgresql-13.4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package postgresql-13.4 E: Coul

Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"

 "Additionally, while reading the next chapter, Server Setup and Operation, is recommended if you are using a binary package the setup and operational environment it creates is likely to be somewhat different than what is described in this documentation.  Please read the documentation for the

Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"

On Wed, Nov 2, 2022 at 6:22 PM David G. Johnston wrote: > Some repetition of what Adrian just posted ahead... > > On Wed, Nov 2, 2022 at 3:31 PM Bryn Llewellyn wrote: > >> >> How can it be that the PG doc itself leads you by the hand to a regime >> where you need to use undocumented features? >>

Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"

Some repetition of what Adrian just posted ahead... On Wed, Nov 2, 2022 at 3:31 PM Bryn Llewellyn wrote: > > I did exactly that. And I selected "Linux" and under that "Ubuntu". Notice > that I did NOT select "Debian", though it was on offer, because that's not > what I have. If Ubuntu and Debian

Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"

On 11/2/22 15:31, Bryn Llewellyn wrote: david.g.johns...@gmail.com EARLIER wrote: A strange mutual misunderstanding has arisen here. I suppose that it must be my fault. I have no interest whatsoever in "going down to first principles". And I most certainl

Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"

> david.g.johns...@gmail.com EARLIER wrote: > > The postgres o/s user should be able to login using peer. It is a one-way > idea though. Wanting to login using peer says nothing about whether the user > getting that capability should be allowed to mess with the running server in > the operating

Re: Reducing bandwidth usage of database replication

On 11/2/22 09:56, Sascha Zenglein wrote: Hi all, I want to use the postgres-native logical replication to have multiple clients receive and send data to a central database. Real-time is far less important than network usage, and with my current test setup it appears both instances communicate

Reducing bandwidth usage of database replication

Hi all, I want to use the postgres-native logical replication to have multiple clients receive and send data to a central database. Real-time is far less important than network usage, and with my current test setup it appears both instances communicate frequently if a subscription is active, ev