| From: | Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Vik Fearing <vik(at)postgresfriends(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Doc fix and adjustment for MERGE command |
| Date: | 2022-09-09 11:58:48 |
| Message-ID: | 256e5614-3167-6783-c536-3607155e7f0d@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-09-09 11:54Z, Alvaro Herrera wrote:
> On 2022-Sep-08, Vik Fearing wrote:
>
>> On 9/7/22 22:51, Vitaly Burovoy wrote:
>>> Hello hackers!
>>>
>>> Reading docs for the MERGE statement I've found a little error: a
>>> semicolon in middle of a statement and absence of a semicolon in the end
>>> of it.
>>>
>>> Key words in subqueries are written in uppercase everywhere in the docs
>>> but not in an example for MERGE. I think it should be adjusted too.
>
>> I agree with both of these patches (especially the semicolon part which is
>> not subjective).
>
> OK, pushed both together.
>
Thank you!
=)
--
Best regards,
Vitaly Burovoy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2022-09-09 12:06:47 | Re: confirmed_flush_lsn shows LSN of the data that has not yet been received by the logical subscriber. |
| Previous Message | Alvaro Herrera | 2022-09-09 11:58:39 | Re: MERGE and parsing with prepared statements |