Re: Make COPY format extendable: Extract COPY TO format implementations
От | Sutou Kouhei |
---|---|
Тема | Re: Make COPY format extendable: Extract COPY TO format implementations |
Дата | |
Msg-id | 20250617.085037.540717523379608629.kou@clear-code.com обсуждение исходный текст |
Ответ на | Re: Make COPY format extendable: Extract COPY TO format implementations (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
Re: Make COPY format extendable: Extract COPY TO format implementations
|
Список | pgsql-hackers |
Hi, In <CAD21AoBwxgfkMYxgPWyrLG-r8-ptVKjd=jhncY_QAaVJYhQQdw@mail.gmail.com> "Re: Make COPY format extendable: Extract COPY TO format implementations" on Thu, 12 Jun 2025 10:00:12 -0700, Masahiko Sawada <sawada.mshk@gmail.com> wrote: >> So, my opinion is to rely on _PG_init(), with a shared ID if you want >> to expose the method used somewhere for monitoring tools. You could >> as well implement the simpler set of APIs that allocates IDs local to >> each backend, like EXPLAIN, then consider later if shared IDs are >> really needed. The registration APIs don't have to be fixed in time >> across releases, they can be always improved in steps as required. >> What matters is ABI compatibility in the same major version once it is >> released. > > +1 to start with a simpler set of APIs. OK. I'll implement the initial version with this design. (Allocating IDs local not shared.) Thanks, -- kou
В списке pgsql-hackers по дате отправления: