Problems with PostgreSQL on Google compute engine

the incident. Thanks. Josef Machytka

Re: strange locks on PG 11 with Golang programs

On Mon, 9 Mar 2020 at 09:58, Julien Rouhaud wrote: > The query displayed is just the query currently executing, but if the > connection is in a transaction the problematic lock could have been > acquired by > any previously executed query. Did you check in pg_stat_activity if the > connection i

strange locks on PG 11 with Golang programs

o by blocked by copy commands running on other tables. This is shown by the same select from PG wiki for blocking queries. All this stuff runs from golang programs. So maybe problem is not on PostgreSQL but in golang libraries? Thank you for any suggestions Josef Machytka Berlin

Re: error when creating logical replication slot

se processes several thousands of inserts each minute, most of them just 1 record in separate transaction - those are metric data from web widgets. JM On Mon, 28 Jan 2019 at 15:15, Tom Lane wrote: > Josef Machytka writes: > > I am implementing logical replication and today durin

error when creating logical replication slot

nt to the context. Could someone please explain to what does this mean? I cannot afford to have errors on production. Many thanks Josef Machytka Berlin

Re: PostgreSQL logical replication depends on WAL segments?

Thanks, I see... So if I understand it correctly - since I have quite big >> partitions like ~30 GB each in one parent table and from ~1GB to ~5 GB in >> several others I presume I had to set wal_keep_segments to some really high >> number and stop our security cronjob cleaning old WAL segments (be

Re: PostgreSQL logical replication depends on WAL segments?

Hi guys, thank you very much for all information. I learned my lesson regarding cronjob cleaning old WAL logs... There is one other interesting problem I have found today and I would like to ask you about you opinion. On logical master I found this morning big flood of these messages in postgresql

Re: PostgreSQL logical replication depends on WAL segments?

> https://www.postgresql.org/docs/11/logical-replication-architecture.html > > Thanks, I see... So if I understand it correctly - since I have quite big partitions like ~30 GB each in one parent table and from ~1GB to ~5 GB in several others I presume I had to set wal_keep_segments to some really h

PostgreSQL logical replication depends on WAL segments?

work perfectly although there cannot be all WAL segments for today available on the logical master. But I am unable to publish older data... Thanks for help. Josef Machytka