| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Vinayak <vinpokale(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] VACUUM Progress Checker. |
| Date: | 2015-12-02 18:33:28 |
| Message-ID: | CA+TgmoZR7D-rvobCSTn4F85N6Vfds7Qy3fmpw6aeMLibLxECGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 30, 2015 at 9:10 PM, Vinayak <vinpokale(at)gmail(dot)com> wrote:
> Thanks for the v7.
> Please check the comment below.
> -Table name in the vacuum progress
>
> + snprintf(progress_message[0], PROGRESS_MESSAGE_LENGTH, "%s.%s",
> schemaname,relname);
Uh, I hope that line doesn't appear in the patch. We're scarcely
likely to commit anything that has such an obvious SQL-injection risk
built into it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-12-02 18:42:01 | Re: [PROPOSAL] VACUUM Progress Checker. |
| Previous Message | Robert Haas | 2015-12-02 18:31:11 | Re: psql ignores failure to open -o target file |