| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Önder Kalacı <onderkalaci(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres |
| Date: | 2016-02-04 14:16:16 |
| Message-ID: | CAM3SWZTYhyxDFp_=hz052+vosgRhNOWmzs7SoGW-krmbW4998Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Feb 4, 2016 at 4:11 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Can you add code to execute the resulting statements? Because obviously
> just seeing the output ain't enough. Seems like an easily repeatable
> error, and the regression test scase ought to be pretty easy with a DO
> and a loop.
What do you mean?
The stored rules whose output was modified as part of the fix are
actually executed already -- no change there. Önder's complaint was
that deparsing doesn't work. It was not that stored rules were ever
independently broken.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-02-04 14:18:05 | Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres |
| Previous Message | Amit Kapila | 2016-02-04 13:19:13 | Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |