Re: REINDEX CONCURRENTLY and indisreplident

2020-06-04 Thread Michael Paquier
On Thu, Jun 04, 2020 at 11:23:36AM +0900, Michael Paquier wrote: > On Wed, Jun 03, 2020 at 12:40:38PM -0300, Euler Taveira wrote: > > On Wed, 3 Jun 2020 at 03:54, Michael Paquier wrote: > >> I have bumped into $subject, causing a replica identity index to > >> be considered as dropped if running R

Re: REINDEX CONCURRENTLY and indisreplident

2020-06-03 Thread Michael Paquier
On Wed, Jun 03, 2020 at 12:40:38PM -0300, Euler Taveira wrote: > On Wed, 3 Jun 2020 at 03:54, Michael Paquier wrote: >> I have bumped into $subject, causing a replica identity index to >> be considered as dropped if running REINDEX CONCURRENTLY on it. This >> means that the old tuple information

Re: REINDEX CONCURRENTLY and indisreplident

2020-06-03 Thread Euler Taveira
On Wed, 3 Jun 2020 at 03:54, Michael Paquier wrote: > Hi all, > > I have bumped into $subject, causing a replica identity index to > be considered as dropped if running REINDEX CONCURRENTLY on it. This > means that the old tuple information would get lost in this case, as > a REPLICA IDENTITY US

REINDEX CONCURRENTLY and indisreplident

2020-06-02 Thread Michael Paquier
Hi all, I have bumped into $subject, causing a replica identity index to be considered as dropped if running REINDEX CONCURRENTLY on it. This means that the old tuple information would get lost in this case, as a REPLICA IDENTITY USING INDEX without a dropped index is the same as NOTHING. Attach