Request a Demo
Home   >   mailing lists

Re: REPACK (CONCURRENTLY) can lose data in pg_dump output - Mailing list pgsql-hackers

From shihao zhong
Subject Re: REPACK (CONCURRENTLY) can lose data in pg_dump output
Date
Msg-id CAGRkXqQ05fEx7QdfbMtsYu4GxaeAcYRGn0rd0Ot-=ZsSpC0fyA@mail.gmail.com
Whole thread
In response to Re: REPACK (CONCURRENTLY) can lose data in pg_dump output  (Sami Imseih <samimseih.pg@gmail.com>)
List pgsql-hackers
Tree view
Hi Thom,

In my understanding, this is an expected beahcior as you mentioned,

A fix is already proposed for v20. 0008 in Antonin's "REPACK
enhancements" series, "Make REPACK (CONCURRENTLY) MVCC-safe", carries
the visibility info over to the new table [1][2]. Jochen hit the same
problem on -bugs with a repeatable read session[3].

[1] https://commitfest.postgresql.org/patch/6957/
[2] https://www.postgresql.org/message-id/224072.1789577949@localhost
[3] https://www.postgresql.org/message-id/0865e13a-da93-4ad1-8b93-7b54a1628f04@jbitc.de

Regards,
Shihao
 

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation
Next
From: Bharath Rupireddy
Date:
Subject: Re: [PATCH] Refactor remaining zero-fill relation extensions to use smgrzeroextend()