| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bernd Helmle <mailings(at)oopsware(dot)de>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |
| Date: | 2009-01-25 21:40:34 |
| Message-ID: | 3073cc9b0901251340y1747c277l6118ac1e2604a2eb@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Sun, Jan 25, 2009 at 11:47 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> This would all be a little easier to accomplish if the behavior were
> made to be implicit in the rewriter (ie, rewrite instead of throwing a
> "no rule" error), since then there is no persistent state that a GUC or
> reloption would have to try to add or get rid of.
why we don't follow this path from the beggining?
what are the pros and cons of this?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2009-01-26 09:50:21 | pginstaller - pginst: Ship the updated version of gettext, as required |
| Previous Message | Alvaro Herrera | 2009-01-25 21:20:00 | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2009-01-25 23:57:56 | Lock Wait Statistics (next commitfest) |
| Previous Message | Alex Hunsaker | 2009-01-25 21:32:00 | Re: Meridiem markers (was: [BUGS] Incorrect "invalid AM/PM string" error from to_timestamp) |