| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Lyes Ameddah <lyes(dot)amd(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14941: Vacuum crashes |
| Date: | 2017-12-14 16:05:42 |
| Message-ID: | AD80AE03-8A5D-40A2-99C9-C26646489E49@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 12/11/17, 9:41 PM, "Masahiko Sawada" <sawada(dot)mshk(at)gmail(dot)com> wrote:
> I also reviewed the patches.
Thanks for taking a look.
> For 0003 patch, if we do VACUUM (NOWAIT) to whole database we don't
> get the above WARNING messages, but I think we should get them. The
> reported issue also did VACUUM FULL and REINDEX to whole database.
> Especially when VACUUM to whole database the information of skipped
> relations would be useful for users.
Perhaps we could attempt to construct the RangeVar just before
logging in this case.
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | thomas.berger | 2017-12-14 18:05:21 | BUG #14975: [pgrpms] make build10 for postgresql fails |
| Previous Message | Bossart, Nathan | 2017-12-14 15:35:39 | Re: BUG #14941: Vacuum crashes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2017-12-14 16:10:38 | Re: procedures and plpgsql PERFORM |
| Previous Message | Bossart, Nathan | 2017-12-14 15:35:39 | Re: BUG #14941: Vacuum crashes |