Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6 - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6
Date
Msg-id 53235DB3.7060804@agliodbs.com
Whole thread Raw
In response to 9a57858f1103b89a5674f0d50c5fe1f756411df6  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6
List pgsql-hackers
Alvaro, All:

Can someone help me with what we should tell users about this issue?

1. What users are especially likely to encounter it?  All replication
users, or do they have to do something else?

2. What error messages will affected users get?  A link to the reports
of this issue on pgsql lists would tell me this, but I'm not sure
exactly which error reports are associated.

3. If users have already encountered corruption due to the fixed issue,
what do they need to do after updating?  re-basebackup?


-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: jsonb and nested hstore
Next
From: Jeff Janes
Date:
Subject: Re: Auto-tuning work_mem and maintenance_work_mem