PostgreSQL

23 December 2025 07:13

i'm pretty sure it's English only in here

PostgreSQL

22 December 2025 12:36

If there's another edition of "Community Summit" at pgconf.dev, what are topics you would like to see discussed?

PostgreSQL

20 December 2025 15:15

You are mentioning about reconfiguring

PostgreSQL

20 December 2025 14:50

No you don't need to

PostgreSQL

18 December 2025 12:30

There is a mailing list on the postgresql website

PostgreSQL

16 December 2025 19:03

Need to convert stored procedures from plsql to redshift sql ie postgress sql anyone providing support ping me

PostgreSQL

10 December 2025 13:04

Can I ask you guys which tools you're using for ETL/migrations?
I mostly go with Apache Nifi but I wonder what other people are using for their daily work

PostgreSQL

10 December 2025 13:02

But unless it's that particular case i wouldn't find a use case for it, and it's just promoting the secondary so nothing amazing or particular

PostgreSQL

10 December 2025 13:01

Yeah, except that the data will come from the secondary

PostgreSQL

10 December 2025 13:00

Switching two times the timelines

PostgreSQL

10 December 2025 12:59

btw - im aware of logical replication
im just playing around with physical replication now

PostgreSQL

10 December 2025 12:55

How can I achieve something like this? if it's even possible?
I thought in case it's part of replication slot it will save the last state to replicate from

PostgreSQL

10 December 2025 12:52

Removing the standby.signal will make the timelines diverge

PostgreSQL

08 December 2025 13:33

For low-volume low-reliability DBs — yes.

PostgreSQL

08 December 2025 12:20

Thanks, Jamie, it looks like 1 database per postgresql cluster is the best option.

PostgreSQL

23 December 2025 07:04

It's hard to translate so don't read this if u can't.

Постгрес.

Уровень repeatable read устраняет фантомное чтение в том смысле, что если другая транзакция во время текущей записала что-то, текущая этого не увидит и закомитит то что хочет, что может вызвать логические проблемы.

Уровень serializable не позволяет закоммитить текущую транзакцию, если какая-то другая сделала то, что для текущей транзакции бы вызвало фантомное чтение (если бы был уровень read committed).

Это так?

PostgreSQL

21 December 2025 09:54

csv, awk/sed, duckdb 😄

PostgreSQL

20 December 2025 14:51

However, depending on the database size it might be worth to stop it and resync using basebackup

PostgreSQL

20 December 2025 14:20

While performing vacuum full on primary whether we need to stop the replica

PostgreSQL

18 December 2025 12:25

Hi where I can find pg careers in Europe?

PostgreSQL

15 December 2025 07:00

Hi i am Giving postgresql DBA offline interview suport in Hyderabad, call:8309555894

PostgreSQL

10 December 2025 13:02

Simple answer: Streaming replication keeps a 1:1 copy of the cluster. No way around it. So no, it's not possible.

PostgreSQL

10 December 2025 13:01

Useful if, for example, your data sits in the same place the secondary is. WAL streaming could be faster (considering wal is chunks of compressed data) than moving the original data and adding it in the primary

PostgreSQL

10 December 2025 13:00

so this would be like just creating the table on the current master , no?

PostgreSQL

10 December 2025 12:59

You can, however, promote the secondary, create your tables, then make the primary a standby and sync it, then make the primary again primary, and switch back once again the secondary to make it secondary again

PostgreSQL

10 December 2025 12:58

There is no way to merge back to primary after the standby diverges, unless you use something like pg_rewind but that moves you back in time, it doesn't integrate the changes

PostgreSQL

10 December 2025 12:53

Corrected, timeline switch happens on promote

PostgreSQL

10 December 2025 12:51

Is it possible to remove the standby.signal from replica in order to create some tables only for replica, and then touch standby.signal and start the replica again? will it work? or it will damage the WAL order?

PostgreSQL

08 December 2025 13:25

Well in that case you will waste a little of ram because shared_buffer is assigned by one cluster and it tends to be a large memory segment. Every case has its drawbacks and your best choice will depend on your use case

PostgreSQL

08 December 2025 11:40

Point in time recovery impacts to the whole instance so you would recover every database.