| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Breakage with VACUUM ANALYSE + partitions |
| Date: | 2016-04-06 00:57:00 |
| Message-ID: | 20160406005700.GA1664259@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, Apr 04, 2016 at 12:45:25PM -0400, Robert Haas wrote:
> Backends shouldn't be requesting nonexistent blocks from a relation -
> higher-level safeguards, like holding AccessExclusiveLock before
> trying to complete a DROP or TRUNCATE - are supposed to prevent that.
> If this patch is causing us to hold onto smgr references to a relation
> on which we no longer hold locks, I think that's irretrievably broken
> and should be reverted. I really doubt this will be the only thing
> that goes wrong if you do that.
+1
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D | 2016-04-06 01:53:31 | Re: BUG #14062: pg_dump dies after dumping first 60 gigabytes of text for large table |
| Previous Message | John R Pierce | 2016-04-05 23:03:25 | Re: pg_upgrade on Windows |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-04-06 01:29:13 | Re: Timeline following for logical slots |
| Previous Message | Craig Ringer | 2016-04-06 00:12:35 | Re: Timeline following for logical slots |