| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | lemes(dot)marcelo26(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Alignment issue at 43.10. Trigger Functions |
| Date: | 2022-12-02 10:42:34 |
| Message-ID: | 7A23D4FE-9004-4867-A418-76E9F737A8C6@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
> On 18 Nov 2022, at 07:21, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> On Thu, 2022-11-17 at 18:14 +0000, PG Doc comments form wrote:
>> Page: https://www.postgresql.org/docs/13/plpgsql-trigger.html
>>
>> Type alignment issue for salary at "Example 43.4. A PL/pgSQL Trigger
>> Function for Auditing":
>>
>> CREATE TABLE emp_audit(
>> operation char(1) NOT NULL,
>> stamp timestamp NOT NULL,
>> userid text NOT NULL,
>> empname text NOT NULL,
>> salary integer
>> );
>
> Attached is a patch to fix that.
There was a second occurrence of the above, as well as one table which had no
vertical alignment at all. I fixed these and applied your patch to master.
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2022-12-02 12:33:46 | Re: Alignment issue at 43.10. Trigger Functions |
| Previous Message | Laurenz Albe | 2022-12-01 21:21:54 | Re: nextval parameter is not clear |