From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
Cc: | Emanuel Calvo <emanuel(dot)calvo(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Patch for CREATE RULE sgml -- Was in: [DOCS] |
Date: | 2014-03-22 06:32:45 |
Message-ID: | CAB7nPqTje7T1VeQX_gz12MYqt0H-ZLkaT8h17bXjmtsi3ZAURw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Sat, Mar 22, 2014 at 11:18 AM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
> On Fri, Mar 21, 2014 at 8:15 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>>
>> On Sat, Mar 22, 2014 at 12:56 AM, Emanuel Calvo
>> <emanuel(dot)calvo(at)2ndquadrant(dot)com> wrote:
>> > I realized that the output of the CREATE RULE has not a detailed
>> > output for the "events" parameter.
>> >
>> The list of events possible is already listed in the section
>> "Parameters" => "event":
>
> AFAIU, the synopsis is used to build the help command (\h) in psql.
> Currently in that help the events doesn't appear.
> btw, CREATE TRIGGER already looks this way:
> http://www.postgresql.org/docs/current/static/sql-createtrigger.html
You are right, I forgot this one... In this case patch 2 could be backpatched...
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2014-03-22 10:14:57 | START_REPLICATION TIMELINE |
Previous Message | Jaime Casanova | 2014-03-22 02:18:45 | Re: Patch for CREATE RULE sgml -- Was in: [DOCS] |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2014-03-22 07:31:00 | Re: ALTER TABLE lock strength reduction patch is unsafe Reply-To: |
Previous Message | Tom Lane | 2014-03-22 05:32:32 | Re: Partial index locks |