| From: | Kasahara Tatsuhito <kasahara(dot)tatsuhito(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Small and unaffected typo in pg_logical_slot_get_changes_guts() |
| Date: | 2022-02-16 04:25:09 |
| Message-ID: | CAP0=ZV+eCAsrktQnrnh4mOXBkOU8KQEritG_vtxmOyVYMu6D1A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi !
2022年2月16日(水) 11:42 Michael Paquier <michael(at)paquier(dot)xyz>:
>
> On Wed, Feb 16, 2022 at 11:27:58AM +0900, Kasahara Tatsuhito wrote:
> > Since commit dd04e958c8b03c0f0512497651678c7816af3198,
> > tuplestore_donestoring() seems to be left only for compatibility, so
> > it looks like it can be removed from the core code, except for the
> > header (tuplestore.h).
>
> FWIW, it looks sensible to me to just do the cleanup you are
> suggesting here on HEAD, aka keeping the compatibility macro in the
> header, but wiping out any references of it in the C code. That
> reduces the chances of copy-pasting it around for no effect. Would
> you like to write a patch?
Thanks for the reply. The patch is attached.
Remove all references to tuplestore_donestoring() except for the header.
Best regards,
--
Tatsuhito Kasahara
kasahara.tatsuhito _at_ gmail.com
| Attachment | Content-Type | Size |
|---|---|---|
| remove_tuplestore_donestoring.patch | application/octet-stream | 11.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-02-16 04:58:10 | Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set |
| Previous Message | Andres Freund | 2022-02-16 04:19:30 | Re: USE_BARRIER_SMGRRELEASE on Linux? |