| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logical decoding doc |
| Date: | 2014-03-19 14:27:01 |
| Message-ID: | CA+TgmoaR9Q1mGbFqEWnzaTFxEHggxivZmV+b2qt9J6NZscYdWQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 18, 2014 at 7:27 PM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
> Maybe this is to demonstrating "peek ahead" does not consume changes,
> but IMO this is a little bit confusing for readers and I think there's
> a room to enhance the second sql session comment for example:
I didn't write that text, but yeah, that was my interpretation of why
it was like that.
> postgres=# -- Again you can also peek ahead in the change stream without consuming changes
I don't especially like that particular text, but perhaps it could be
made more clear in some way.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-03-19 14:55:51 | Re: Re: Leaking regexp_replace in 9.3.1 ? (was: [HACKERSUninterruptable regexp_replace in 9.3.1 ?) |
| Previous Message | Pavel Stehule | 2014-03-19 13:00:46 | Re: Review: plpgsql.extra_warnings, plpgsql.extra_errors |