Re: pg_logical_emit_message() misses a XLogFlush()
От | Amit Kapila |
---|---|
Тема | Re: pg_logical_emit_message() misses a XLogFlush() |
Дата | |
Msg-id | CAA4eK1JbWkUwAudnTC7P6vgwLycTDELduSNM2nL-+PmEJ6O4Eg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_logical_emit_message() misses a XLogFlush() (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: pg_logical_emit_message() misses a XLogFlush()
|
Список | pgsql-hackers |
On Mon, Oct 16, 2023 at 12:47 PM Michael Paquier <michael@paquier.xyz> wrote: > > On Fri, Oct 13, 2023 at 03:20:30PM +0530, Amit Kapila wrote: > > I would prefer to associate the new parameter 'flush' with > > non-transactional messages as per the proposed patch. > > Check. > > > Is there a reason to make the functions strict now when they were not earlier? > > These two are already STRICT on HEAD: > =# select proname, provolatile, proisstrict from pg_proc > where proname ~ 'message'; > proname | provolatile | proisstrict > -------------------------+-------------+------------- > pg_logical_emit_message | v | t > pg_logical_emit_message | v | t > (2 rows) > oh, I misunderstood the default. > > An updated version is attached. How does it look? > LGTM. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: