On Fri, Sep 21, 2018 at 09:09:36AM +0200, Adrien NAYRAT wrote:
> Thanks! As it could happen even on previous version, should we
> backpatch for the documentation?
I have patched HEAD, and then down until conflicts happened, which is
v10, thinking about it as a documentation improvement. The
On 9/21/18 8:13 AM, Michael Paquier wrote:
On Thu, Sep 20, 2018 at 08:23:45AM +0200, Adrien Nayrat wrote:
Yes, here is the patch.
Thanks Adrien. I have reworded a bit the thing, fixed a typo, and
pushed down to v11 where this applied without conflicts.
thanks! As it could happen even on
On Thu, Sep 20, 2018 at 08:23:45AM +0200, Adrien Nayrat wrote:
> Yes, here is the patch.
Thanks Adrien. I have reworded a bit the thing, fixed a typo, and
pushed down to v11 where this applied without conflicts.
--
Michael
signature.asc
Description: PGP signature
On 9/19/18 4:53 AM, Michael Paquier wrote:
> On Tue, Sep 18, 2018 at 12:32:54PM +0200, Adrien NAYRAT wrote:
>> A few days ago I was surprised a CREATE TABLE containing FK constraint was
>> stuck due to an automatic vacuum freeze (which took ShareUpdateExclusiveLock
>> if I remember) on referenced
On Tue, Sep 18, 2018 at 12:32:54PM +0200, Adrien NAYRAT wrote:
> A few days ago I was surprised a CREATE TABLE containing FK constraint was
> stuck due to an automatic vacuum freeze (which took ShareUpdateExclusiveLock
> if I remember) on referenced table.
Right. See the top of vacuum_rel()
