Re: pgsql: Allow multiple xacts during table sync in logical replication.
От | Amit Kapila |
---|---|
Тема | Re: pgsql: Allow multiple xacts during table sync in logical replication. |
Дата | |
Msg-id | CAA4eK1Km3NsEK-6rS+H8JBcY15AhOG3rYuSGZ5GZphZfoSju1A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgsql: Allow multiple xacts during table sync in logical replication. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pgsql: Allow multiple xacts during table sync in logical replication.
Re: pgsql: Allow multiple xacts during table sync in logical replication. |
Список | pgsql-committers |
On Sat, Feb 13, 2021 at 4:20 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Don't do that. Quite aside from the inconsistency, this is pretty > darn unsafe coding technique, because there is exactly nothing > guaranteeing that the caller passes a buffer of the length the > function expects. > > I'm not real sure that you could expect a compiler warning for that > even if you'd put the length declaration where callers could see it. > So personally I'd avoid hard-wiring NAMEDATALEN into this API at all, > and have the caller pass sizeof(its buffer) instead. > Thanks for pointing it out. I'll look into this. BTW, how one can check such reports, do one need to check all make logs for buildfarm members? -- With Regards, Amit Kapila.
В списке pgsql-committers по дате отправления: