Request a Demo
Home   >   mailing lists

Re: Handle concurrent drop when doing whole database vacuum - Mailing list pgsql-hackers

From surya poondla
Subject Re: Handle concurrent drop when doing whole database vacuum
Date
Msg-id CAOVWO5q++nEqiNSY837gySa2wjHODyMiPnMA8i3bK4JYpb_2Og@mail.gmail.com
Whole thread
List pgsql-hackers
Tree view
Hi ChangAo,

Thank you for incorporating the changes.

I applied and tested the v3 patch, it works all good.

Both permutations (vacuum and analyze) pass and the expected output now asserts 's1: WARNING:  skipping vacuum of "foo"  and' 's1: WARNING:  skipping analyze of "foo" ' respectively which looks correct.

Regarding the backpatch, I agree this is a long standing bug, the test spec might need to change as there is no pg_maintain, but the fix itself should apply cleanly.

Overall, the patch looks in good shape.
Thank you for working on this issue.

You can create a commitfest entry.

Regards,
Surya Poondla

pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Small patch to improve safety of utf8_to_unicode().
Next
From: Christophe Pettus
Date:
Subject: Re: The PostgreSQL C Dialect