Horton

Amit Kapila

amit.kapila16@gmail.com

Email: amit.kapila16@gmail.com
Name: Amit Kapila
Messages: 0
First message: —
Last message: —

Recent messages

DateSubject
2026-05-31T11:54:08Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-30T18:21:10Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-29T22:18:41Z Re: [Patch] Fix check_pub_rdt bypass when origin is set in same ALTER SUBSCRIPTION
2026-05-29T18:47:49Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-29T15:39:18Z Re: Adding REPACK [concurrently]
2026-05-29T03:17:13Z Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
2026-05-28T23:41:34Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-28T03:34:08Z Re: Adding REPACK [concurrently]
2026-05-28T00:31:59Z Re: Adding REPACK [concurrently]
2026-05-27T23:08:11Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-27T22:09:45Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-27T21:26:47Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-27T00:44:29Z Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server
2026-05-26T23:39:34Z Re: Bound memory usage during manual slot sync retries
2026-05-26T16:40:19Z Re: Bound memory usage during manual slot sync retries
2026-05-26T02:03:48Z Re: Bound memory usage during manual slot sync retries
2026-05-23T15:40:08Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-23T15:29:35Z Re: Adding REPACK [concurrently]
2026-05-15T09:23:30Z Re: Bound memory usage during manual slot sync retries
2026-05-14T10:48:33Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-14T07:02:25Z Re: Adding REPACK [concurrently]
2026-05-13T12:34:17Z Re: Adding REPACK [concurrently]
2026-05-12T09:21:15Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-12T09:19:15Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-12T07:57:29Z Re: Adding REPACK [concurrently]
2026-05-11T04:25:27Z Re: DOCS - CREATE PUBLICATION ... EXCEPT has no mention on what happens after drop/create tables
2026-05-10T11:31:04Z Re: Adding REPACK [concurrently]
2026-05-10T11:24:29Z Re: Adding REPACK [concurrently]
2026-05-08T12:25:12Z Re: Adding REPACK [concurrently]
2026-05-08T09:07:45Z Re: Include schema-qualified names in publication error messages.
2026-05-07T12:36:08Z Re: Include schema-qualified names in publication error messages.
2026-05-07T10:07:54Z Re: Include schema-qualified names in publication error messages.
2026-05-07T06:46:34Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-06T11:01:19Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-06T10:31:41Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-06T05:17:20Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-06T03:57:30Z Re: Include schema-qualified names in publication error messages.
2026-05-05T10:42:08Z Re: Include schema-qualified names in publication error messages.
2026-05-05T05:25:44Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-05T04:57:47Z Re: Include schema-qualified names in publication error messages.
2026-05-05T02:56:38Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-04T12:23:04Z Re: Support logical replication of DDLs, take2
2026-05-04T11:28:53Z Re: Proposal: Conflict log history table for Logical Replication
2026-05-04T08:57:26Z Re: StringInfo fixes, v19 edition. Plus a few oddities
2026-05-01T10:41:39Z Re: [PATCH] Fix stale relation close in sequence synchronization
2025-12-30T06:55:37Z Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2025-12-28T06:48:19Z Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2025-12-24T09:12:15Z Re: [Patch] add new parameter to pg_replication_origin_session_setup
2025-12-24T08:26:01Z Re: Orphaned records in pg_replication_origin_status after subscription drop
2025-12-24T06:28:21Z Re: [bug fix] prepared transaction might be lost when max_prepared_transactions is zero on the subscriber