| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table, log i |
| Date: | 2017-12-07 02:42:12 |
| Message-ID: | E1E33F47-1B82-47EF-BA48-BBF2421AE3DF@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 12/6/17, 8:25 PM, "Robert Haas" <robertmhaas(at)gmail(dot)com> wrote:
> Please give me a little time to see if I can speed up this test enough
> to fix this problem. If that doesn't work out, then we can rip this
> out.
Just in case it got missed earlier, here’s a patch that speeds it
up enough to pass with CLOBBER_CACHE_ALWAYS enabled. Instead of
doing database-wide operations, it just uses a partitioned table.
Nathan
| Attachment | Content-Type | Size |
|---|---|---|
| fix_vacuum_concurrent_drop_test_v1.patch | application/octet-stream | 5.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-12-07 03:08:38 | Re: [HACKERS] [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Previous Message | Robert Haas | 2017-12-07 02:25:21 | Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table, log i |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-12-07 03:08:38 | Re: [HACKERS] [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Previous Message | Robert Haas | 2017-12-07 02:25:21 | Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table, log i |