Re: Add CREATE support to event triggers

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add CREATE support to event triggers
Date: 2014-01-09 17:58:41
Message-ID: 20140109175840.GQ6840@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas escribió:
> On Wed, Jan 8, 2014 at 10:27 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:

> > Hmm. This seems like a reasonable thing to do, except that I would like
> > the "output" to always be the constant, and have some other way to
> > enable the clause or disable it. With your "present" boolean:
> > so
> >
> > "if_not_exists": {"output": "IF NOT EXISTS",
> > "present": true/false}
>
> Why not:
>
> "if_not_exists": true/false

Yeah, that's another option. If we do this, though, the expansion
function would have to know that an "if_not_exist" element expands to IF
NOT EXISTS. Maybe that's okay. Right now, the expansion function is
pretty stupid, which is nice.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-01-09 18:03:08 Re: integrate pg_upgrade analyze_new_cluster.sh into vacuumdb
Previous Message Steeve Lennmark 2014-01-09 17:58:22 [PATCH] Relocation of tablespaces in pg_basebackup