experts,
We migrated our database from Oracle to Postgresql recently, we used to
turn on Oracle session trace(that will capture all activities, SQL
statements, waiting, waiting time), to do living troubleshooting. could
you direct any similar tracing in Postgresql v13 , v14.
Thanks,
James
On Mon, 22 Jan 2024 at 05:50, Chris Angelico wrote:
>
> On Mon, 22 Jan 2024 at 05:25, Justin wrote:
> > Adding a primary key will fix this issue. Note PG 16 can use indexes to
> > find qualifying rows when a table's replica is set to full.
>
> I'll try dropping the table, creating it again with
On Mon, 22 Jan 2024 at 05:25, Justin wrote:
>
> When using replica set to full this kicks off a full table scan for each
> update or delete this is very expensive. If there are no errors being
> reported you will find it is working but hung doing full scans. Inserts are
> just appended to e
On Sat, Jan 20, 2024, 5:43 PM Chris Angelico wrote:
> PostgreSQL 15 on Debian, both ends of replication.
>
> I'm doing logical replication in a bit of a complex setup. Not sure
> how much of this is relevant so I'll give you a lot of detail; sorry
> if a lot of this is just noise.
>
> * Bidirecti
