Re: MError after replication in postgresql

Hi, There are many causes of this issue. One possible solution to handle this issue is to make sure that proper dynamic linking as follows: export LD_LIBRARY_PATH=/path/to/pgsql/lib:$LD_LIBRARY_PATH On Wed, 25 Sept 2024 at 10:35, Danish Hajwane wrote: > > Hi Team, > > We are getting error after

Re: Repeatable Read Isolation Level "transaction start time"

"Peter J. Holzer" writes: > On 2024-09-25 13:53:30 -0700, Christophe Pettus wrote: >> This might well be a failure of imagination on my part, but when would >> it pragmatically matter that the snapshot is taken at the first >> statement as opposed to at BEGIN? > It may make a difference if you're

Re: Repeatable Read Isolation Level "transaction start time"

On 2024-09-25 13:53:30 -0700, Christophe Pettus wrote: > > On Sep 25, 2024, at 13:49, Greg Sabino Mullane wrote: > > BEGIN ISOLATION MODE REPEATABLE READ SNAPSHOT NOW; > > This might well be a failure of imagination on my part, but when would > it pragmatically matter that the snapshot is tak

Re: Repeatable Read Isolation Level "transaction start time"

On Wed, Sep 25, 2024 at 4:54 PM Christophe Pettus wrote: > On Sep 25, 2024, at 13:49, Greg Sabino Mullane wrote: > > BEGIN ISOLATION MODE REPEATABLE READ SNAPSHOT NOW; > > This might well be a failure of imagination on my part, but when would it > pragmatically matter that the snapshot is ta

Re: PgBackRest : Restore to a checkpoint shows further transactions

On Wed, Sep 25, 2024 at 2:13 AM KK CHN wrote: > PgBackRest : I tried to restore the latest backup taken at my RepoServer > to a testing EPAS server freshly deployed . > ... > Now I comment out the archive command in the test EPAS server > postgresql.conf and started the EPAS server. > * To d

Re: Repeatable Read Isolation Level "transaction start time"

On Wed, Sep 25, 2024 at 4:50 PM Greg Sabino Mullane wrote: > Since transactions should be "as short as possible, without being too >>> short", how much time is there between when you run "BEGIN;" and the first >>> "work statement"? >>> >> > I don't know that it really matters. For something autom

Re: Repeatable Read Isolation Level "transaction start time"

> On Sep 25, 2024, at 13:49, Greg Sabino Mullane wrote: > BEGIN ISOLATION MODE REPEATABLE READ SNAPSHOT NOW; This might well be a failure of imagination on my part, but when would it pragmatically matter that the snapshot is taken at the first statement as opposed to at BEGIN?

Re: Synchronize the dump with a logical slot with --snapshot

Hi Team --snapshot=snapshotname (Use the specified synchronized snapshot when making a dump of the database This option is useful when needing to synchronize the dump with a logical replication slot) as per the pgdg How do we synchronize the dump with a logical replication slot with --snapshot?

Re: Repeatable Read Isolation Level "transaction start time"

> > Since transactions should be "as short as possible, without being too >> short", how much time is there between when you run "BEGIN;" and the first >> "work statement"? >> > I don't know that it really matters. For something automated, it would be a few milliseconds. Either way, I'm sure most p

Re: Repeatable Read Isolation Level "transaction start time"

On Wed, Sep 25, 2024 at 4:23 PM Greg Sabino Mullane wrote: > On Wed, Sep 25, 2024 at 1:53 PM Tom Lane wrote: > >> Because we're not going to analyze the statement in the amount of depth >> needed to make that distinction before we crank up the >> transactional machinery. If it says SELECT, it g

Re: Repeatable Read Isolation Level "transaction start time"

On Wed, Sep 25, 2024 at 1:53 PM Tom Lane wrote: > Because we're not going to analyze the statement in the amount of depth > needed to make that distinction before we crank up the > transactional machinery. If it says SELECT, it gets a snapshot. > Ok, thanks. So to the original poster's point, p

Re: Repeatable Read Isolation Level "transaction start time"

On Wed, Sep 25, 2024 at 1:53 PM Tom Lane wrote: > Ron Johnson writes: > > But why does "SELECT 1;" need a snapshot? Heck, why does "SELECT > > ;" need a snapshot? > > Because we're not going to analyze the statement in the amount of > depth needed to make that distinction before we crank up the

Re: Repeatable Read Isolation Level "transaction start time"

Ron Johnson writes: > But why does "SELECT 1;" need a snapshot? Heck, why does "SELECT > ;" need a snapshot? Because we're not going to analyze the statement in the amount of depth needed to make that distinction before we crank up the transactional machinery. If it says SELECT, it gets a snaps

Re: Repeatable Read Isolation Level "transaction start time"

On Wed, Sep 25, 2024 at 1:45 PM Adrian Klaver wrote: > > > On 9/25/24 10:22 AM, Greg Sabino Mullane wrote: > > On Tue, Sep 24, 2024 at 10:28 AM Tom Lane > > wrote: > > > > It's even looser than that, really: it's the first statement that > > requires an MVCC sn

Re: Repeatable Read Isolation Level "transaction start time"

On 9/25/24 10:22 AM, Greg Sabino Mullane wrote: On Tue, Sep 24, 2024 at 10:28 AM Tom Lane > wrote: It's even looser than that, really: it's the first statement that requires an MVCC snapshot. Hmso why does "SELECT 1;" work as a transaction start marker

Re: Repeatable Read Isolation Level "transaction start time"

On Tue, Sep 24, 2024 at 10:28 AM Tom Lane wrote: > It's even looser than that, really: it's the first statement that > requires an MVCC snapshot. Hmso why does "SELECT 1;" work as a transaction start marker then, as opposed to "SHOW work_mem;", which does not? Do we simply consider anything

Re: PgBackRest : Restore to a checkpoint shows further transactions

On 9/24/24 23:12, KK CHN wrote: List, PgBackRest :  I tried to restore the latest backup taken at my WHen I issue a query  to select few rows  To my surprise  I am seeing the records with columns with time stamp up to a time 10.36:11:968  and 10:36:13.363 : How did this happen ?   I sp

Re: Logical Replication Delay

On Sat, Sep 21, 2024 at 3:08 PM Ramakrishna m wrote: > I would greatly appreciate any suggestions you may have to help avoid > logical replication delays, whether through tuning database or operating > system parameters, or any other recommendations > In addition to the things already answered:

Re: MError after replication in postgresql

On Wed, 2024-09-25 at 10:57 +0530, Danish Hajwane wrote: > We are getting error after doing replication on posrgresql 16.3 (OS is HP UX) > error is regarding Libpq library, we are unable to start sync getting error > > FATAL: could not connect to the primary server : libpq is incorrectly linked >

Re: glibc updarte 2.31 to 2.38

Hi Adrian, > On 22 Sep 2024, at 18:53, Adrian Klaver wrote: > > https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-HIGHLIGHTS > > Add a builtin platform-independent collation provider (Jeff Davis) > > This supports C and C.UTF-8 collations. I must admit that I haven't read the read